smithery/gtmagents

market-signal-tracker

Operating system for logging market/competitive signals with severity, confidence, and routing.

Installation

$ npx skills add smithery/gtmagents --skill market-signal-tracker

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,515 B
  • docs SUMMARY.md 124 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.