playbooks

home / skills / gtmagents / gtm-agents / market-signal-tracker

market-signal-tracker skill

/plugins/competitive-intelligence/skills/market-signal-tracker

This skill helps you monitor market signals across competitors, route insights to owners, and track actions with SLA-driven workflows.

npx playbooks add skill gtmagents/gtm-agents --skill market-signal-tracker

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.5 KB
---
name: market-signal-tracker
description: Operating system for logging market/competitive signals with severity,
  confidence, and routing.
---

# Market Signal Tracker Skill

## When to Use
- Monitoring competitor launches, pricing moves, org shifts, funding, or partner announcements.
- Tracking analyst coverage, customer chatter, or social sentiment around competitors.
- Ensuring signals route to the right owners with context and deadlines.

## Framework
1. **Signal Intake** – capture source, timestamp, competitor, category (product, pricing, GTM, talent, regulation).
2. **Severity & Confidence** – rate potential impact, confidence level, and affected product/segment.
3. **Routing** – assign owners (product, enablement, comms, exec) with SLA + follow-up notes.
4. **Action Status** – track planned/active/completed actions linked to each signal.
5. **Reporting** – weekly digest summarizing net-new signals, escalations, and outstanding actions.

## Templates
- Signal log spreadsheet or Notion database with views by competitor/category.
- Weekly digest template with highlights, escalations, and recommended actions.
- Action tracker with owner, due date, and dependency fields.

## Tips
- Automate ingestion by connecting RSS, alerts, and social monitoring; maintain manual overrides for high-sensitivity items.
- Keep a rolling 90-day archive to reference trends and repeat patterns.
- Pair with `analyze-competitive-landscape` and `run-win-loss-program` for holistic perspective.

---

Overview

This skill is an operating system for logging market and competitive signals with structured severity, confidence, and routing. It centralizes intake, prioritization, and owner-driven actions so teams respond quickly to launches, pricing moves, funding, org changes, and sentiment shifts. The goal is fast, auditable signal-to-action workflows that feed weekly reporting and decision-making.

How this skill works

Signals are captured with source, timestamp, competitor, and category (product, pricing, GTM, talent, regulation). Each signal is scored for severity and confidence, tagged to affected products or segments, and routed to named owners with SLA and follow-up notes. Actions are tracked as planned/active/completed and rolled into a weekly digest that highlights net-new signals, escalations, and outstanding items.

When to use it

  • Monitoring competitor product launches, pricing changes, partner moves, or funding events
  • Tracking analyst coverage, customer chatter, or social sentiment that could affect GTM
  • Routing time-sensitive alerts to product, comms, enablement, or exec owners
  • Documenting systemic trends with a rolling archive for repeated patterns
  • Coordinating cross-functional response plans and post-action reviews

Best practices

  • Standardize intake fields (source, category, severity, confidence, affected segment) to enable filtering and reporting
  • Automate ingestion from RSS, alerts, and social feeds but keep manual review for high-sensitivity signals
  • Assign clear owners with SLA and required follow-up notes to avoid dropped items
  • Maintain a 90-day rolling archive to spot repeats and measure signal recurrence
  • Use templated weekly digests and action trackers to force closure and visible accountability

Example use cases

  • Sales leader receives routing for a competitor price cut and launches enablement and objection-handling content within SLA
  • Product manager tags a competitor feature release with high severity and triggers a triage meeting and roadmap review
  • Marketing pulls weekly digest to brief executives on escalations and recommended comms
  • Customer success flags rising negative sentiment about a competitor integration and schedules outreach to at-risk accounts
  • RevOps correlates signal frequency to win-loss outcomes to refine monitoring thresholds

FAQ

How are severity and confidence defined?

Severity measures potential business impact on product/segment; confidence rates source reliability and corroboration. Use simple low/medium/high scales with rules for escalation.

Can ingestion be automated?

Yes—connect RSS, alerts, and social monitors to auto-create signals. Always allow manual override and human validation for sensitive items.

What reporting cadence is recommended?

Produce a weekly digest with net-new signals, escalations, and outstanding actions; escalate critical items immediately.