market-signal-tracker

Log and route competitive market signals with severity, confidence, and owner assignments.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill market-signal-tracker-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: market-signal-tracker
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/company-deep-research/market-signal-tracker
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill market-signal-tracker-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Competitive and market intelligence often arrives scattered across alerts, social chatter, and analyst notes, making it easy to miss critical competitor moves or fail to route them to the right owner. This Skill provides a structured operating system for capturing, scoring, routing, and reporting on market signals so nothing falls through the cracks. ## Core Features & Use Cases - Signal Intake & Classification: Capture source, timestamp, competitor, and category (product, pricing, GTM, talent, regulation) for every signal. - Severity & Confidence Scoring: Rate potential impact, confidence level, and affected product or segment to prioritize response. - Routing & Action Tracking: Assign owners across product, enablement, comms, and exec teams with SLAs, due dates, and action status tracking. - Weekly Reporting: Generate digests summarizing net-new signals, escalations, and outstanding actions. - Use Case: A competitor announces a surprise price cut. Log the signal, rate it high-severity for your mid-market segment, route it to product marketing with a 48-hour SLA, and include it in the weekly digest with recommended counter-messaging. ## Quick Start Log a new competitive signal about a rival's pricing change, rate its severity and confidence, and route it to the product marketing owner with a follow-up deadline.

Frequently Asked Questions about market-signal-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track competitor product launches and pricing changes?

Capture each competitor move as a signal with source, timestamp, competitor name, and category such as product or pricing. Then rate severity and confidence, assign an owner with an SLA, and track the resulting action to completion.

What categories should I use for competitive intelligence signals?

Use five core categories: product, pricing, GTM, talent, and regulation. These cover launches, pricing moves, organizational shifts, funding, partner announcements, and regulatory changes affecting competitors.

How do I route market signals to the right team?

Assign each signal an owner from product, enablement, comms, or exec teams based on its category and severity. Include an SLA and follow-up notes so the owner knows the expected response timeline and context.

Can I automate competitor monitoring with RSS and alerts?

Yes, automate ingestion by connecting RSS feeds, alerts, and social monitoring tools to feed the signal log. Keep manual overrides for high-sensitivity items that need human judgment before routing.

How long should I keep competitive signal history?

Maintain a rolling 90-day archive of signals to reference trends and repeat patterns. This window balances recency with enough history to spot recurring competitor behaviors.