Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Competitive Teardown

  • 599 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

competitive-teardown is a Claude Code skill that helps developers run structured competitive analysis surfacing actionable gaps and opportunities before committing to product direction.

About

competitive-teardown is a product research skill providing structured competitive analysis templates for developers and PMs evaluating market positioning before build commitments. The skill includes SWOT analysis tables with evidence, impact, and exploitability columns covering strengths, weaknesses, opportunities, and threats for named competitors. Developers reach for competitive-teardown when comparing feature sets, identifying API or capability gaps, or documenting competitor weaknesses with sourced evidence. Output templates standardize analyst, date, and version metadata so findings remain auditable across product decisions.

  • Ready-to-use SWOT Analysis template with evidence and impact scoring
  • Porter's Five Forces template adapted for product and market assessment
  • Structured tables that force evidence-based conclusions instead of vague opinions
  • Helps identify differentiators and strategic advantages in under 30 minutes

Competitive Teardown by the numbers

  • 599 all-time installs (skills.sh)
  • Ranked #667 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill competitive-teardown

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs599
repo stars23.5k
Security audit3 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you run structured competitive product analysis?

Run structured competitive analysis that surfaces actionable gaps and opportunities before committing to product direction.

Who is it for?

Developers and PMs evaluating competitor products who need evidence-backed SWOT teardowns before choosing feature direction.

Skip if: Post-launch analytics, automated web scraping pipelines, or engineering implementation tasks with no competitive research requirement.

When should I use this skill?

The user asks for competitive analysis, competitor teardown, SWOT comparison, or market gap research before product decisions.

What you get

SWOT analysis documents, competitor evidence tables, gap assessments, and prioritized opportunity rankings.

  • SWOT analysis document
  • Competitor evidence tables
  • Gap and opportunity summary

Files

SKILL.mdMarkdownGitHub ↗

Competitive Teardown

Tier: POWERFUL Category: Product Team Domain: Competitive Intelligence, Product Strategy, Market Analysis

---

When to Use

  • Before a product strategy or roadmap session
  • When a competitor launches a major feature or pricing change
  • Quarterly competitive review
  • Before a sales pitch where you need battle card data
  • When entering a new market segment

---

Teardown Workflow

Follow these steps in sequence to produce a complete teardown:

1. Define competitors — List 2–4 competitors to analyze. Confirm which is the primary focus. 2. Collect data — Use references/data-collection-guide.md to gather raw signals from at least 3 sources per competitor (website, reviews, job postings, SEO, social). _Validation checkpoint: Before proceeding, confirm you have pricing data, at least 20 reviews, and job posting counts for each competitor._ 3. Score using rubric — Apply the 12-dimension rubric below to produce a numeric scorecard for each competitor and your own product. _Validation checkpoint: Every dimension should have a score and at least one supporting evidence note._ 4. Generate outputs — Populate the templates in references/analysis-templates.md (Feature Matrix, Pricing Analysis, SWOT, Positioning Map, UX Audit). 5. Build action plan — Translate findings into the Action Items template (quick wins / medium-term / strategic). 6. Package for stakeholders — Assemble the Stakeholder Presentation using outputs from steps 3–5.

---

Data Collection Guide

Full executable scripts for each source are in references/data-collection-guide.md. Summaries of what to capture are below.

1. Website Analysis

Key things to capture:

  • Pricing tiers and price points
  • Feature lists per tier
  • Primary CTA and messaging
  • Case studies / customer logos (signals ICP)
  • Integration logos
  • Trust signals (certifications, compliance badges)

2. App Store Reviews

Review sentiment categories:

  • Praise → what users love (defend / strengthen these)
  • Feature requests → unmet needs (opportunity gaps)
  • Bugs → quality signals
  • UX complaints → friction points you can beat them on

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.

3. Job Postings (Team Size & Tech Stack Signals)

Signals from job postings:

  • Engineering volume → scaling vs. consolidating
  • Specific tech mentions → stack (React/Vue, Postgres/Mongo, AWS/GCP)
  • Sales/CS ratio → product-led vs. sales-led motion
  • Data/ML roles → upcoming AI features
  • Compliance roles → regulatory expansion

4. SEO Analysis

SEO signals to capture:

  • Top 20 organic keywords (intent: informational / navigational / commercial)
  • Domain Authority / backlink count
  • Blog publishing cadence and topics
  • Which pages rank (product pages vs. blog vs. docs)

5. Social Media Sentiment

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.

---

Scoring Rubric (12 Dimensions, 1-5)

#Dimension1 (Weak)3 (Average)5 (Best-in-class)
1FeaturesCore only, many gapsSolid coverageComprehensive + unique
2PricingConfusing / overpricedMarket-rate, clearTransparent, flexible, fair
3UXConfusing, high frictionFunctionalDelightful, minimal friction
4PerformanceSlow, unreliableAcceptableFast, high uptime
5DocsSparse, outdatedDecent coverageComprehensive, searchable
6SupportEmail only, slowChat + email24/7, great response
7Integrations0-5 integrations6-2526+ or deep ecosystem
8SecurityNo mentionsSOC2 claimedSOC2 Type II, ISO 27001
9ScalabilityNo enterprise tierMid-market readyEnterprise-grade
10BrandGeneric, unmemorableDecent positioningStrong, differentiated
11CommunityNoneForum / SlackActive, vibrant community
12InnovationNo recent releasesQuarterlyFrequent, meaningful

Example completed row (Competitor: Acme Corp, Dimension 3 – UX):

DimensionAcme Corp ScoreEvidence
UX2App 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.

---

Templates

Full template markdown is in references/analysis-templates.md. Abbreviated reference below.

Feature Comparison Matrix

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

Pricing Analysis

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.

SWOT Analysis

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.).

Positioning Map

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.

UX Audit Checklist

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.

Action Items

HorizonEffortExamples
Quick wins (0–4 wks)LowAdd review badges, publish comparison landing page
Medium-term (1–3 mo)ModerateLaunch free tier, improve onboarding TTFV, add top-requested integration
Strategic (3–12 mo)HighEnter new market, build API v2, achieve SOC2 Type II

Stakeholder Presentation (7 slides)

1. Executive Summary — Threat level (LOW/MEDIUM/HIGH/CRITICAL), top strength, top opportunity, recommended action 2. Market Position — 2x2 positioning map 3. Feature Scorecard — 12-dimension radar or table, total scores 4. Pricing Analysis — Comparison table + key insight 5. UX Highlights — What they do better (3 bullets) vs. where we win (3 bullets) 6. Voice of Customer — Top 3 review complaints (quoted or paraphrased) 7. Our Action Plan — Quick wins, medium-term, strategic priorities; Appendix with raw data

Related Skills

  • Product Strategist (product-team/product-strategist/) — Competitive insights feed OKR and strategy planning
  • Landing Page Generator (product-team/landing-page-generator/) — Competitive positioning informs landing page messaging

Related skills

FAQ

What templates does competitive-teardown include?

competitive-teardown includes SWOT analysis templates with tabular evidence for strengths, weaknesses, opportunities, and threats. Each row tracks impact or exploitability ratings and sourced data points for competitor comparisons.

When should competitive-teardown be used in a project?

competitive-teardown fits before product direction commits, when developers or PMs need structured competitor research that surfaces actionable gaps and opportunities rather than ad hoc competitor notes.

Is Competitive Teardown safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Productivity & Planningresearchautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.