competitor-signal-tracker
$
npx mdskill add mohitagw15856/pm-claude-skills/competitor-signal-trackerTurn scattered competitor information into structured strategic intelligence — not just "what they did" but "what it means for us."
SKILL.md
.github/skills/competitor-signal-trackerView on GitHub ↗
--- 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
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign 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.
- ab-test-plannerDesign 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.
- accessibility-auditGenerate 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.
- account-planBuild 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.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.