Skip to content
Back to skills

Competitor Signal Tracker

ASecurity

Analyse competitor moves and surface strategic implications for your product. Use when asked to track competitor signals, analyse a competitor announcement, understand what a competitor is doing strategically, or produce a competitive intelligence report. Produces a categorised signal analysis with threat ratings, roadmap implications, and recommended responses.

  • 1,330 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
data-aigoreact

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Competitor Signal Tracker?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Competitor Signal Tracker
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mohitagw15856-competitor-signal-tracker/badge)](https://www.skillsdirectory.com/skills/mohitagw15856-competitor-signal-tracker)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: competitor-signal-tracker
description: "Analyse competitor moves and surface strategic implications for your product. Use when asked to track competitor signals, analyse a competitor announcement, understand what a competitor is doing strategically, or produce a competitive intelligence report. Produces a categorised signal analysis with threat ratings, roadmap implications, and recommended responses."
---

# Competitor Signal Tracker Skill

Turn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us."

## Required Inputs

Ask the user for these if not provided:
- **Competitor name(s)** and the signals/updates to analyse
- **Your product's current roadmap or strategic priorities** (to assess relevance)
- **Time period** the signals cover (this week, this month, etc.)

## Signal Categories to Track
- **Product signals:** New features, removals, UX changes, beta programmes
- **Pricing signals:** Changes to tiers, free limits, enterprise terms
- **Hiring signals:** Job postings that reveal strategic bets (e.g., hiring ML engineers = AI investment)
- **Partnership signals:** Integrations, acquisitions, ecosystem moves
- **Messaging signals:** Changes in positioning, target audience, value proposition

## Process
1. For each competitor update provided, categorise the signal type
2. Assess: Is this reactive (responding to market) or proactive (setting direction)?
3. Rate strategic threat level: High / Medium / Low / Watch
4. Connect to your roadmap: does this accelerate, validate, or challenge any of your bets?
5. Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further
6. **Validate** — Confirm every High threat has a specific recommended response with an owner. "Monitor" is not an acceptable response for High-rated threats.

## Output Structure

### Competitive Intelligence Report — [Date]

#### [Competitor Name]
**Signal:** [What they did]
**Signal Type:** [Product / Pricing / Hiring / Partnership / Messaging]
**Reactive or Proactive:** [assessment]
**Threat Level:** [High / Medium / Low / Watch]
**Implication for Us:** [Specific connection to our roadmap or strategy]
**Recommended Response:** [Action + owner + timeline]

#### Strategic Summary
[2-3 sentences on the overall competitive landscape shift this period]

## Quality Checks

- [ ] Every signal is categorised (not just described)
- [ ] Threat level is justified — not assigned arbitrarily
- [ ] High-threat signals have specific recommended responses (not "monitor")
- [ ] Implications connect to specific roadmap items or strategic bets
- [ ] Strategic summary gives a landscape-level view, not just a list of individual signals

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…