competitive-intelligence-monitor
$
npx mdskill add mohitagw15856/pm-claude-skills/competitive-intelligence-monitorTurn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us."
SKILL.md
.github/skills/competitive-intelligence-monitorView on GitHub ↗
--- name: competitive-intelligence-monitor description: "Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary." --- # Competitive Intelligence Monitor Skill Turn scattered competitor updates into structured weekly intelligence — not just "what they did" but "what changed since last week and what it means for us." ## Required Inputs Ask the user for these if not provided: - **Competitors to monitor** (list of company names) - **Your current roadmap or strategic priorities** (to assess relevance of signals) - **Previous brief or last run summary** (for diff mode — what's new vs. last time) - **Time period** (this week, this month) ## Signal Categories to Monitor - **Product signals:** New features, removals, UX changes, beta programmes - **Pricing signals:** Changes to tiers, free limits, enterprise terms - **Hiring signals:** Job postings revealing strategic bets - **Partnership signals:** Integrations, acquisitions, ecosystem moves - **Messaging signals:** Changes in positioning, audience, value proposition ## Process ### First Run (Full Report) 1. For each competitor provided, scan all five signal categories 2. Categorise each signal found 3. Assess: reactive (responding to market) or proactive (setting direction)? 4. Rate threat level: High / Medium / Low / Watch 5. Connect each signal to a specific item on the provided roadmap 6. Recommend response: Accelerate / Deprioritise / Monitor / Investigate 7. **Validate** — Every High signal must have a specific recommended action and owner. "Monitor" is only acceptable for Low and Watch ratings. ### Subsequent Runs (Diff Only) 1. Compare current signals against previous run summary 2. Output ONLY what is new or changed since last run 3. Flag if a previously Low signal has escalated to High 4. Keep output under 300 words — brevity is the point ## Output Structure ### Competitive Intelligence Brief — [Date] **New Since Last Run:** [n signals] #### 🔴 High Priority **[Competitor]:** [Signal] → [Implication] → [Recommended action + owner] #### 🟡 Watch **[Competitor]:** [Signal] → [Why it matters now] #### ✅ No Change [Competitors with no new signals this week] **This Week's Strategic Summary:** [2 sentences max — what is the overall competitive landscape doing?] ## Quality Checks - [ ] Every High-priority signal has a specific response action and owner - [ ] Signals are categorised (not just listed as "they did X") - [ ] Roadmap connections are specific (not "generally relevant") - [ ] Diff mode output is under 300 words - [ ] Strategic summary describes the landscape trend, not just repeats 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.