.claude/skills/competitive-teardown/SKILL.md
Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates. Use when conducting competitor analysis, comparing products against competitors, researching the competitive landscape, building battle cards for sales, preparing for a product strategy or roadmap session, responding to a competitor's new feature or pricing change, or performing a quarterly competitive review.
npx skillsauth add bsweet101/buckstop-rebrand competitive-teardownInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Tier: POWERFUL
Category: Product Team
Domain: Competitive Intelligence, Product Strategy, Market Analysis
Follow these steps in sequence to produce a complete teardown:
references/data-collection-guide.md to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social).references/analysis-templates.md (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit).Full executable scripts for each source are in
references/data-collection-guide.md. Summaries of what to capture are below.
Key things to capture:
Review sentiment categories:
Sample App Store query (iTunes Search API):
GET https://itunes.apple.com/search?term=<competitor_name>&entity=software&limit=1
# Extract trackId, then:
GET https://itunes.apple.com/rss/customerreviews/id=<trackId>/sortBy=mostRecent/json?l=en&limit=50
Parse entry[].content.label for review text and entry[].im:rating.label for star rating.
Signals from job postings:
SEO signals to capture:
Capture recent mentions via Twitter/X API v2, Reddit, or LinkedIn. Look for recurring praise, complaints, and feature requests. See references/data-collection-guide.md for API query examples.
| # | Dimension | 1 (Weak) | 3 (Average) | 5 (Best-in-class) | |---|-----------|----------|-------------|-------------------| | 1 | Features | Core only, many gaps | Solid coverage | Comprehensive + unique | | 2 | Pricing | Confusing / overpriced | Market-rate, clear | Transparent, flexible, fair | | 3 | UX | Confusing, high friction | Functional | Delightful, minimal friction | | 4 | Performance | Slow, unreliable | Acceptable | Fast, high uptime | | 5 | Docs | Sparse, outdated | Decent coverage | Comprehensive, searchable | | 6 | Support | Email only, slow | Chat + email | 24/7, great response | | 7 | Integrations | 0-5 integrations | 6-25 | 26+ or deep ecosystem | | 8 | Security | No mentions | SOC2 claimed | SOC2 Type II, ISO 27001 | | 9 | Scalability | No enterprise tier | Mid-market ready | Enterprise-grade | | 10 | Brand | Generic, unmemorable | Decent positioning | Strong, differentiated | | 11 | Community | None | Forum / Slack | Active, vibrant community | | 12 | Innovation | No recent releases | Quarterly | Frequent, meaningful |
Example completed row (Competitor: Acme Corp, Dimension 3 – UX):
| Dimension | Acme Corp Score | Evidence | |-----------|----------------|---------| | UX | 2 | App Store reviews cite "confusing navigation" (38 mentions); onboarding requires 7 steps before TTFV; no onboarding wizard; CC required at signup. |
Apply this pattern to all 12 dimensions for each competitor.
Full template markdown is in
references/analysis-templates.md. Abbreviated reference below.
Rows: core features, pricing tiers, platform capabilities (web, iOS, Android, API).
Columns: your product + up to 3 competitors.
Score each cell 1–5. Sum to get total out of 60.
Score legend: 5=Best-in-class, 4=Strong, 3=Average, 2=Below average, 1=Weak/Missing
Capture per competitor: model type (per-seat / usage-based / flat rate / freemium), entry/mid/enterprise price points, free trial length.
Summarize: price leader, value leader, premium positioning, your position, and 2–3 pricing opportunity bullets.
For each competitor: 3–5 bullets per quadrant (Strengths, Weaknesses, Opportunities for us, Threats to us). Anchor every bullet to a data signal (review quote, job posting count, pricing page, etc.).
2x2 axes (e.g., Simple ↔ Complex / Low Value ↔ High Value). Place each competitor and your product. Bubble size = market share or funding. See references/analysis-templates.md for ASCII and editable versions.
Onboarding: TTFV (minutes), steps to activation, CC-required, onboarding wizard quality.
Key workflows: steps, friction points, comparative score (yours vs. theirs).
Mobile: iOS/Android ratings, feature parity, top complaint and praise.
Navigation: global search, keyboard shortcuts, in-app help.
| Horizon | Effort | Examples | |---------|--------|---------| | Quick wins (0–4 wks) | Low | Add review badges, publish comparison landing page | | Medium-term (1–3 mo) | Moderate | Launch free tier, improve onboarding TTFV, add top-requested integration | | Strategic (3–12 mo) | High | Enter new market, build API v2, achieve SOC2 Type II |
product-team/product-strategist/) — Competitive insights feed OKR and strategy planningproduct-team/landing-page-generator/) — Competitive positioning informs landing page messagingdata-ai
Use when the user asks to design database schemas, plan data migrations, optimize queries, choose between SQL and NoSQL, or model data relationships.
tools
Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analyzing customer accounts, reviewing retention metrics, scoring at-risk customers, or when the user mentions churn, customer health scores, upsell opportunities, expansion revenue, retention analysis, or customer analytics. Runs three Python CLI tools to produce deterministic health scores, churn risk tiers, and prioritized expansion recommendations across Enterprise, Mid-Market, and SMB segments.
development
Build, measure, and evolve company culture as operational behavior — not wall posters. Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, and cultural rituals by stage. Use when building company values, assessing culture health, designing cultural rituals, creating culture codes, handling culture clashes, or when user mentions culture, values, culture debt, founder culture, or culture code.
testing
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.