New to Claude Skills? Learn how to install them →

alirezarezvani on GitHub

Competitive Teardown

Free

Streamline competitor analysis for strategic insights.

Get this skill

Free · Opens the source repo

What Competitive Teardown does

Competitive Teardown is a Python-based skill designed to assist product teams in conducting thorough analyses of competitor products and companies. By synthesizing data from various sources such as pricing pages, app store reviews, job postings, SEO signals, and social media, this skill generates structured competitive intelligence. It helps users create detailed feature comparison matrices, SWOT analyses, positioning maps, UX audits, and pricing model breakdowns, all tailored to enhance strategic decision-making.

The skill is particularly useful for product managers and strategists who need to understand the competitive landscape before making key business decisions. It provides a systematic workflow that guides users through defining competitors, collecting relevant data, scoring products across multiple dimensions, and generating actionable insights. Each step is supported by templates and guides, ensuring that users can effectively translate their findings into stakeholder presentations and action item roadmaps.

With a focus on structured data collection and analysis, Competitive Teardown enables teams to respond swiftly to market changes, such as new competitor features or pricing adjustments. It serves as a comprehensive toolkit for anyone involved in product strategy, sales preparation, or market entry analysis. The skill's emphasis on validation checkpoints ensures that the data collected is robust and reliable, making the resulting analyses credible and actionable.

In summary, Competitive Teardown is an essential tool for product teams looking to gain a competitive edge through informed decision-making and strategic planning. By leveraging its capabilities, teams can better position their products in the market and identify opportunities for growth and improvement.

When to use it

Use this skill when preparing for product strategy sessions, responding to competitor actions, or conducting quarterly reviews of the competitive landscape.

When not to use it

This skill may not be suitable for quick, informal assessments or when detailed competitor analysis is not required.

What you can build with it

Preparing for a Product Strategy Session

Utilize the skill to gather insights on competitors before making strategic decisions regarding your product roadmap.

Responding to Competitor Changes

Quickly analyze a competitor's new feature or pricing change to adjust your strategy accordingly.

Conducting a Quarterly Review

Perform a comprehensive review of the competitive landscape every quarter to stay informed and agile.

How to install Competitive Teardown

View source

1. Install with the skills CLI

npx skills add alirezarezvani/claude-skills/competitive-teardown --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by alirezarezvani

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

Frequently asked questions about Competitive Teardown

Similar skills