competitor-teardown
$
npx mdskill add mohitagw15856/pm-claude-skills/competitor-teardownThis skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.
SKILL.md
.github/skills/competitor-teardownView on GitHub ↗
--- name: competitor-teardown description: "Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations." --- # Competitor Teardown Skill This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions. ## Required Inputs Ask the user for these if not provided: - **Your product** (name + one-line description) - **Competitors to analyse** (list 2–5 names; if not provided, ask) - **Analysis depth** (quick overview / detailed teardown) - **Primary use case for this analysis** (e.g. sales enablement, investor deck, internal strategy, product planning) ## Output Structure ### 1. Competitive Landscape Overview One paragraph summarising the market dynamic: who the key players are, how the market is segmented, and where the white space sits. Keep this under 150 words — it's the exec summary. ### 2. Positioning Map Describe a 2x2 positioning map in text form (since you can't render images): - Define the two axes relevant to this market (e.g. "Ease of Use vs. Depth of Features" or "Price vs. Enterprise Readiness") - Place each competitor in one quadrant with a one-sentence rationale - Place the user's product and highlight the strategic implication ### 3. Feature Comparison Table | Feature / Capability | [Your Product] | [Competitor A] | [Competitor B] | [Competitor C] | |---|---|---|---|---| | [Feature] | ✅ / ❌ / 🟡 Partial | | | | Use ✅ (has it), ❌ (doesn't have it), 🟡 (partial/limited). Add a "Strategic Notes" column for features where the difference is a significant selling point or risk. Include 10–15 rows. If user hasn't provided feature details, note which cells need to be verified. ### 4. Messaging Analysis For each competitor, analyse their public-facing messaging (website headline, tagline, primary value prop): **[Competitor Name]** - **Their primary claim:** [what they say they do] - **Target audience signal:** [who they seem to be targeting based on language/imagery] - **Emotional hook:** [fear / aspiration / authority / speed / simplicity] - **Gap or weakness in their messaging:** [what they don't address that your product could own] ### 5. SWOT Summary Produce a clean SWOT for the user's product in the context of this competitive landscape: - **Strengths:** [2–3 genuine differentiators] - **Weaknesses:** [2–3 honest gaps or vulnerabilities] - **Opportunities:** [2–3 market gaps or competitor weaknesses to exploit] - **Threats:** [2–3 competitor moves or market shifts to watch] ### 6. Strategic Recommendations 3–5 actionable recommendations based on the analysis. Frame each as: **"Given [observation], [your product] should [action] to [outcome]."** ## Quality Checks - [ ] Axes on positioning map are meaningful and specific to this market - [ ] Feature table includes strategic notes on key differentiators - [ ] Messaging analysis covers all named competitors - [ ] SWOT is honest — Weaknesses and Threats should not be softened - [ ] Recommendations are specific and actionable, not generic strategy advice ## Example Trigger Phrases - "Do a competitor analysis of [Product] vs [Competitor A] and [Competitor B]" - "Tear down [Competitor]'s positioning" - "Give me a competitive landscape for [market]" - "Build a SWOT for our product against [competitor]"
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.