competitive-teardown
by alirezarezvanicompetitive-teardown helps product teams run evidence-backed Competitive Analysis from public competitor signals. It guides data collection from pricing pages, reviews, job posts, SEO/social sources, docs, and changelogs, then produces scored matrices, SWOT, positioning notes, pricing breakdowns, UX observations, action roadmaps, and battle-card inputs.
This skill scores 84/100, making it a solid listing candidate for directory users who need structured competitive intelligence workflows. It provides clear use cases, substantive reference material, and a supporting script, so an agent can execute a teardown with less guesswork than a generic prompt. The main adoption caveats are the missing install guidance and reliance on collecting high-quality external data.
- Strong triggerability: the frontmatter description and “When to Use” section clearly target competitor analysis, battle cards, roadmap sessions, pricing changes, and quarterly reviews.
- Operationally useful workflow: SKILL.md lays out a sequenced teardown process with validation checkpoints and references for data collection, frameworks, templates, and scoring.
- Adds agent leverage beyond a generic prompt through a reusable scoring rubric, structured analysis templates, and a Python competitive matrix builder for weighted comparisons and gap analysis.
- No install command or README is present in the skill directory, so users must rely on repository conventions to adopt it.
- The workflow depends on users or agents gathering current external data from multiple public sources; quality will vary if source access is limited.
Overview of competitive-teardown skill
What competitive-teardown does
competitive-teardown is a product-team skill for turning public competitor signals into structured competitive analysis. It guides an AI agent through defining 2–4 competitors, collecting evidence from pricing pages, reviews, job posts, SEO/social signals, docs, changelogs, and market sources, then producing outputs such as scoring matrices, SWOT analysis, positioning notes, pricing breakdowns, UX observations, and action roadmaps.
Best fit for Competitive Analysis work
The competitive-teardown skill is most useful for product managers, founders, product marketers, strategy teams, and sales enablement teams that need a repeatable Competitive Analysis workflow rather than a one-off opinion. It fits quarterly competitor reviews, new-market research, battle card preparation, response planning after a competitor launch, and roadmap discussions where stakeholders need evidence-backed tradeoffs.
Why this skill is different from a generic prompt
A generic prompt may summarize competitors, but this skill adds a workflow, evidence expectations, analysis templates, scoring rubrics, and a helper script for weighted matrices. The main value is consistency: the same dimensions, source types, and scoring logic can be reused across competitors and review cycles, making the output easier to compare and defend.
Important adoption considerations
This skill depends on the quality of public data you provide or allow the agent to gather. It is not a replacement for win/loss interviews, paid market research, private financial data, or internal customer intelligence. Use it when public competitive evidence is enough to support directional decisions, and label uncertainty when signals are incomplete.
How to Use competitive-teardown skill
competitive-teardown install and repository path
Install the skill from the repository path:
npx skills add alirezarezvani/claude-skills --skill competitive-teardown
After installation, inspect the skill files before relying on the first output. Start with SKILL.md, then read:
references/data-collection-guide.mdfor source types and ethical public-data collectionreferences/scoring-rubric.mdfor the 1–10 scoring model and weighted dimensionsreferences/analysis-templates.mdfor SWOT, Five Forces, battle-card-style structures, and presentation-ready tablesreferences/competitive-analysis-frameworks.mdfor positioning and market structure frameworksscripts/competitive_matrix_builder.pyif you want repeatable weighted scoring from structured JSON
Inputs the skill needs
For strong competitive-teardown usage, provide more than competitor names. Include:
- Your product, category, target segment, and geography
- 2–4 competitors, with one primary competitor if relevant
- Decision context, such as “roadmap planning,” “sales battle card,” or “pricing response”
- Source links already collected, especially pricing, docs, reviews, changelogs, and case studies
- Priority dimensions, such as UX, pricing, integrations, AI features, compliance, onboarding, or enterprise readiness
- Output format, such as executive memo, product roadmap implications, feature matrix, or sales enablement brief
A weak prompt is: “Compare us with Competitor A.”
A stronger prompt is: “Use competitive-teardown to compare our B2B helpdesk product against Zendesk, Intercom, and Freshdesk for mid-market SaaS buyers. Prioritize pricing transparency, AI automation, integrations, onboarding, and enterprise controls. Use public pricing pages, G2 review themes, docs, changelogs, and job postings. Produce a scored matrix, SWOT, positioning gaps, and 30/60/90-day action recommendations.”
Suggested workflow for better results
Run the workflow in stages instead of asking for a finished report immediately:
- Ask the agent to confirm competitors, segment, source plan, and scoring dimensions.
- Collect or approve at least three public sources per competitor.
- Ask for an evidence table before conclusions.
- Generate the competitive matrix using the scoring rubric.
- Request interpretation: gaps, threats, positioning opportunities, and recommended actions.
- Convert the analysis into the final stakeholder format.
This staged approach reduces hallucinated claims and makes it easier to challenge scores before they become recommendations.
Using the matrix builder script
The repository includes scripts/competitive_matrix_builder.py, which can generate weighted competitive matrices from structured competitor data. Use it when you want reproducible scoring rather than a purely narrative report.
Typical usage:
python scripts/competitive_matrix_builder.py competitors.json --format text
You can also apply weights:
python scripts/competitive_matrix_builder.py competitors.json --format text --weights pricing=2,ux=1.5
This is useful when your decision hinges on a few dimensions, such as pricing and onboarding for SMB buyers or compliance and integrations for enterprise buyers.
competitive-teardown skill FAQ
Is competitive-teardown good for beginners?
Yes, if you can provide clear competitors and business context. The references give enough structure for a beginner to produce a usable first analysis. However, scoring still requires judgment. Beginners should ask the agent to show evidence next to every score and to flag low-confidence conclusions.
What makes the skill useful for Competitive Analysis?
The competitive-teardown skill combines collection guidance, templates, frameworks, and a scoring rubric. That matters because Competitive Analysis often fails when teams mix anecdotes, outdated pricing, and unweighted feature opinions. This skill encourages comparable evidence and makes the final output easier to audit.
When should I not use this skill?
Do not use it when you need legally sensitive intelligence, private customer data, confidential competitor information, or definitive market-share numbers without credible sources. It is also a poor fit for analyzing dozens of competitors at once; start with 2–4 and expand only after the scoring model is stable.
Can it create sales battle cards or roadmap recommendations?
Yes. The skill can produce battle-card inputs such as competitor strengths, weaknesses, objection handling, positioning angles, and proof points. For roadmap work, it can highlight feature gaps and strategic threats, but the final prioritization should still include customer value, engineering effort, revenue impact, and company strategy.
How to Improve competitive-teardown skill
Improve competitive-teardown inputs
The fastest way to improve competitive-teardown output is to provide evidence-rich inputs. Instead of pasting only homepage links, include pricing URLs, feature docs, review snippets, recent release notes, target customer examples, integration pages, and screenshots if available. Ask the agent to separate “observed evidence” from “inferred interpretation.”
Prevent common failure modes
Common failures include overvaluing marketing copy, treating old reviews as current truth, comparing products for the wrong buyer segment, and giving precise scores without enough evidence. Prevent this by specifying source dates, customer segment, evaluation criteria, and confidence levels. If pricing is hidden or enterprise-only, require the analysis to say so rather than guessing.
Iterate after the first output
Do not accept the first report as final. Ask follow-up questions such as:
- “Which scores are least supported by evidence?”
- “What would change if the buyer were enterprise rather than SMB?”
- “Which competitor advantage is most defensible?”
- “What claims should sales avoid because evidence is weak?”
- “Turn this into a roadmap risk register with impact and urgency.”
These iterations turn a broad teardown into decision-ready Competitive Analysis.
Customize the rubric to your market
The default rubric is a strong starting point, but your market may need different weights. For developer tools, API quality and documentation may matter more than visual UX. For regulated SaaS, compliance and procurement readiness may dominate. For consumer apps, onboarding, retention signals, app store reviews, and pricing friction may deserve higher weight. Adjust the rubric before scoring so the competitive-teardown guide reflects how your buyers actually choose.