Analyse competitor moves and translate them into strategic
Competitor Signal Tracker Skill
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive…
--- name: competitor-signal-tracker description: "Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners. For a recurring whole-market briefing use competitive-intelligence-monitor instead." --- # 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
Overview
Turn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us."
Manual install (npx, ZIP)
Claude Code
npx skills add mohitagw15856/pm-claude-skills --skill competitor-signal-tracker -g -a claude-codeClaude Code (manual)
mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \
| tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/competitor-signal-trackerWindows (PowerShell)
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/e3ea5a8061a965e5e748/competitor-signal-tracker.zip" -OutFile "$env:TEMP\competitor-signal-tracker.zip"; Expand-Archive "$env:TEMP\competitor-signal-tracker.zip" -DestinationPath "$HOME\.claude\skills" -ForceClaude.ai / desktop
Codex, Cursor, other agents
Connects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md3.6 KB
Read the files here
mohitagw15856/
SKILL.md
Show the full text61 lines
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
- For each competitor update provided, categorise the signal type
- Assess: Is this reactive (responding to market) or proactive (setting direction)?
- Rate strategic threat level: High / Medium / Low / Watch
- Connect to your roadmap: does this accelerate, validate, or challenge any of your bets?
- Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further
- 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]
Anti-Patterns
- Do not rate a signal as High threat without explaining the specific roadmap item or customer segment it threatens — unjustified threat ratings lose credibility over time
- Do not treat a hiring signal as definitive proof of a strategic bet — hiring signals require corroboration from product, messaging, or pricing signals before acting on them
- Do not conflate a competitor's announcement with a competitor's shipped capability — press releases and blog posts often describe aspirations, not production features
- Do not recommend "accelerate existing initiative" for every High signal — sometimes the right response is to differentiate harder in an adjacent area rather than race the competitor directly
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
| 1 | |
| 2 | name competitor-signal-tracker |
| 3 | description "Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners. For a recurring whole-market briefing use competitive-intelligence-monitor instead." |
| 4 | |
| 5 | |
| 6 | # Competitor Signal Tracker Skill |
| 7 | |
| 8 | Turn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us." |
| 9 | |
| 10 | ## Required Inputs |
| 11 | |
| 12 | Ask the user for these if not provided: |
| 13 | **Competitor name(s)** and the signals/updates to analyse |
| 14 | **Your product's current roadmap or strategic priorities** (to assess relevance) |
| 15 | **Time period** the signals cover (this week, this month, etc.) |
| 16 | |
| 17 | ## Signal Categories to Track |
| 18 | **Product signals:** New features, removals, UX changes, beta programmes |
| 19 | **Pricing signals:** Changes to tiers, free limits, enterprise terms |
| 20 | **Hiring signals:** Job postings that reveal strategic bets (e.g., hiring ML engineers = AI investment) |
| 21 | **Partnership signals:** Integrations, acquisitions, ecosystem moves |
| 22 | **Messaging signals:** Changes in positioning, target audience, value proposition |
| 23 | |
| 24 | ## Process |
| 25 | For each competitor update provided, categorise the signal type |
| 26 | Assess: Is this reactive (responding to market) or proactive (setting direction)? |
| 27 | Rate strategic threat level: High / Medium / Low / Watch |
| 28 | Connect to your roadmap: does this accelerate, validate, or challenge any of your bets? |
| 29 | Recommend a response: Accelerate existing initiative / Deprioritise / Monitor / Investigate further |
| 30 | **Validate** — Confirm every High threat has a specific recommended response with an owner. "Monitor" is not an acceptable response for High-rated threats. |
| 31 | |
| 32 | ## Output Structure |
| 33 | |
| 34 | ### Competitive Intelligence Report — [Date] |
| 35 | |
| 36 | #### [Competitor Name] |
| 37 | **Signal:** [What they did] |
| 38 | **Signal Type:** [Product / Pricing / Hiring / Partnership / Messaging] |
| 39 | **Reactive or Proactive:** [assessment] |
| 40 | **Threat Level:** [High / Medium / Low / Watch] |
| 41 | **Implication for Us:** [Specific connection to our roadmap or strategy] |
| 42 | **Recommended Response:** [Action + owner + timeline] |
| 43 | |
| 44 | #### Strategic Summary |
| 45 | [2-3 sentences on the overall competitive landscape shift this period] |
| 46 | |
| 47 | ## Anti-Patterns |
| 48 | |
| 49 | [ ] Do not rate a signal as High threat without explaining the specific roadmap item or customer segment it threatens — unjustified threat ratings lose credibility over time |
| 50 | [ ] Do not treat a hiring signal as definitive proof of a strategic bet — hiring signals require corroboration from product, messaging, or pricing signals before acting on them |
| 51 | [ ] Do not conflate a competitor's announcement with a competitor's shipped capability — press releases and blog posts often describe aspirations, not production features |
| 52 | [ ] Do not recommend "accelerate existing initiative" for every High signal — sometimes the right response is to differentiate harder in an adjacent area rather than race the competitor directly |
| 53 | |
| 54 | ## Quality Checks |
| 55 | |
| 56 | [ ] Every signal is categorised (not just described) |
| 57 | [ ] Threat level is justified — not assigned arbitrarily |
| 58 | [ ] High-threat signals have specific recommended responses (not "monitor") |
| 59 | [ ] Implications connect to specific roadmap items or strategic bets |
| 60 | [ ] Strategic summary gives a landscape-level view, not just a list of individual signals |
| 61 |
Details
- Updated
- Sep 23, 2026
- License
- MIT
- Stars on the repo
- ★ 1,395
- Checked
- Source
- mohitagw15856/pm-claude-skills ↗
- Creator
- mohitagw15856 · 193 listings
Made with competitor-signal-tracker
Competitor Signal Tracker Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Competitor Signal Tracker Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Similar skills
See all →
SkillEstimate the intrinsic value of a public company using DCFCompany valuation
himself65/finance-skills · by himself65Estimate the intrinsic value of a public company using DCF, relative (peer multiple) and sum-of-parts (SOTP) methods, then triangulate to an implied share price with upside/downside versus the current market price. Use this skill whenever the user asks: what is AAPL worth", "valuation of NVDA", "fair value of TSLA", "intrinsic value", DCF for MSFT", "build a DCF", "discounted cash flow", "WACC", "terminal value", implied share price", "upside to fair value", "is X overvalued/undervalued", relative valuation", "peer comparison valuation", "EV/EBITDA target", "SOTP", sum of the parts", "how much is [company] worth", "price target from fundamentals", value this company", or any ticker in the context of computing intrinsic or relative valuation. Default to running ALL three methods (DCF + relative + SOTP-if-applicable) and presenting a blended implied price with a sensitivity table. Do not answer valuation questions from memory — always run the workflow.★ 3.3k GitHub stars
SkillFind keywords a competitor ranks for that the user's siteCompetitor gap
Ryze-AI-Adgent/open-seo-mcp-skills · by Ryze-AI-AdgentFind keywords a competitor ranks for that the user's site doesn't — the content gap, prioritized by volume and winnability. Use when asked "what does competitor.com rank for", "keyword gap vs X", "steal competitor keywords", or "why do they outrank us".★ 3.1k GitHub stars
SkillMine the highest-converting ad angles from customer reviewsAd angle miner
gooseworks-ai/goose-skills · by gooseworks-aiMine the highest-converting ad angles from customer reviews, Reddit complaints, support tickets, and competitor ads. Extracts actual pain language, competitor weaknesses, and outcome phrases that real buyers use. Outputs a ranked angle bank with proof quotes and recommended ad formats per angle.★ 1.2k GitHub stars
SkillAnalyze competitor content coverageCompetitor content intelligence
sandbaseai/sandbase-skills · by sandbaseaiAnalyze competitor content coverage and uncover differentiated content opportunities using web search, page extraction, and DataForSEO content analysis. Use when asked for competitor content research, editorial gap analysis, content brief inputs, or topic whitespace.★ 203 GitHub stars
SkillCreates competitive battlecards for sales deal conversations
growthack88/growth-marketing-os · by growthack88Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per competitor. Outputs a structured markdown battlecard with quick-reference sections for live sales calls. Depends on competitor-research for competitive intelligence and consumes product-messaging, win-loss-analysis, and positioning for framing. Feeds into sales-deck, outreach-emails, and demo-script. Triggered by "battlecard", "competitive intel", "win against [competitor]", or "how do we beat [competitor]".★ 117 GitHub stars
SkillRead your X audience and niche from real dataX audience insights
sergebulaev/x-skills · by sergebulaevRead your X (Twitter) audience and niche from real data. Pull a handle's recent tweets (yours or a competitor's) with likes, replies, and views, see which formats and hooks are working, read the repliers on a tweet (X gates likers, so repliers are the signal), and scan a niche query for top tweets. Powered by Apify, no login. Triggers on "analyze my tweets", "what is working on X", "read the replies", "competitor tweets", "who is engaging". Not for writing a tweet (use x-post-writer).★ 95 GitHub starsMore from mohitagw15856
SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skill
mohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub stars
SkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub stars
SkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub stars
SkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub stars
SkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub stars
SkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars