SkillAgentSearch skills...

competitive-teardown

Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action plans with stakeholder presentation templates.

Install / Use

npx skills add borghei/Claude-Skills --skill competitive-teardown

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Tags

Our assessment of competitive-teardown

competitive-teardown scores 92/100 on our quality scale, 941st of 4,702 Development & Engineering skills we index (top 21%).

Its SKILL.md is 21 KB long, well organised into 46 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so competitive-teardown is actively maintained.
  • Our last check on 2026-10-28 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk β€” read a skill before letting an agent act on it.

competitive-teardown compared with similar skills

All 4 of these similar skills score higher than competitive-teardown; compare them before choosing.

SkillScoreStarsUpdatedFormat
competitive-teardown (this skill)by borghei9281757d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install competitive-teardown?
Run npx skills add borghei/Claude-Skills --skill competitive-teardown. The install tabs above show the steps for each supported agent.
Which AI agents does competitive-teardown work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is competitive-teardown safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is competitive-teardown still maintained?
The repository was last updated about 2 months ago, so competitive-teardown is actively maintained.

name: competitive-teardown description: > Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action plans with stakeholder presentation templates. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: business-growth updated: 2026-03-31 tags: - competitive-intelligence - competitor-analysis - product-strategy - battle-cards - market-analysis

Competitive Teardown

Production-grade competitor analysis framework covering systematic data collection across 6 intelligence sources, a 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audit methodology, and strategic action plans. Produces battle-card-ready output and stakeholder presentation templates.


Table of Contents


When to Use

| Trigger | Teardown Scope | |---------|---------------| | Before product strategy or roadmap session | Full teardown (2-4 competitors) | | Competitor launches major feature or pricing change | Focused teardown (1 competitor, updated dimensions only) | | Quarterly competitive review | Update existing teardowns + trend analysis | | Before a sales pitch (battle card needed) | Single-competitor battle card | | Entering a new market segment | Full teardown of segment incumbents |


Clarify First

Before running the teardown, confirm these inputs. If any is unknown or vague, ASK β€” do not assume:

  • [ ] Competitors + primary focus β€” the 2-4 names and which is the main threat (sets scorecard columns and depth)
  • [ ] Your own product baseline β€” so the 12-dimension scorecard and feature matrix have a "you" column to compare against
  • [ ] Decision this feeds β€” roadmap session, sales battle card, or new-market entry (determines full teardown vs single battle card vs segment incumbents)
  • [ ] Available data sources β€” pricing pages, 50+ reviews, product access (the rubric needs evidence; thin data caps which dimensions are scorable)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the teardown.

Teardown Workflow

Step-by-Step Process

  1. Define competitors -- List 2-4 competitors. Confirm which is the primary focus.
  2. Collect data -- Gather intelligence from at least 3 of the 6 sources per competitor.
  3. Score using rubric -- Apply the 12-dimension rubric to produce a numeric scorecard.
  4. Generate comparison outputs -- Feature matrix, pricing analysis, SWOT, positioning map.
  5. Build action plan -- Translate findings into quick wins, medium-term, and strategic priorities.
  6. Package for stakeholders -- Assemble the presentation or battle card.

Validation Checkpoints

  • Before scoring: Confirm you have pricing data, 20+ user reviews, and recent product data
  • Before action plan: Every dimension should have a score and supporting evidence
  • Before presentation: Every recommendation should tie back to a data point

Data Collection Framework

Source 1: Website and Product Analysis

| Data Point | Where to Find | What It Signals | |-----------|--------------|-----------------| | Pricing tiers and price points | Pricing page | Market positioning, target segment | | Feature lists per tier | Pricing + feature pages | Packaging strategy | | Primary CTA and messaging | Homepage hero | Positioning and ICP | | Case studies and customer logos | Case study page, homepage | Target segments, social proof | | Integration partnerships | Integrations page | Ecosystem strategy | | Trust signals | Footer, security page | Enterprise readiness | | Job postings | Careers page, LinkedIn | Growth direction, tech stack |

Source 2: User Reviews

Platforms: G2, Capterra, TrustRadius, App Store, Product Hunt

| Category | What to Track | Strategic Value | |----------|-------------|-----------------| | Praise themes | What users love (top 5 themes) | Their defensible strengths | | Complaint themes | What users hate (top 5 themes) | Your opportunities | | Feature requests | What users want but do not have | Product roadmap gaps | | Switching mentions | Why users left competitors | Competitive migration paths | | Rating trends | Quarter-over-quarter rating change | Improving or declining |

Sample size target: 50+ reviews per competitor for reliable themes.

Source 3: Job Postings

| Signal | What It Means | |--------|--------------| | High engineering hiring | Product investment, scaling | | AI/ML roles | AI features coming | | Sales team expansion | Moving upmarket or expanding geographically | | Customer success roles | Retention focus, enterprise motion | | Compliance/legal roles | Regulatory expansion | | Reduced postings | Cost cutting, potential contraction |

Source 4: SEO and Content Analysis

| Metric | Tool | Strategic Value | |--------|------|-----------------| | Top 20 organic keywords | Ahrefs, SEMrush, GSC | Content strategy and targeting | | Domain authority | Ahrefs, Moz | Brand strength | | Blog publishing cadence | Manual check | Content investment level | | Ranking pages (product vs blog vs docs) | Ahrefs | Traffic composition |

Source 5: Social Media and Community

| Platform | What to Track | |----------|-------------| | Twitter/X | Product announcements, customer praise, complaints | | Reddit | Honest reviews, comparison threads | | LinkedIn | Thought leadership, hiring signals, employee count | | Community forums | Feature requests, workarounds, power user patterns | | Discord/Slack | Community size, engagement level |

Source 6: Financial and Market Data

| Source | Data Available | |-------|---------------| | Crunchbase | Funding, valuation, investors, employee count | | LinkedIn | Employee count trend (growth proxy) | | Public filings (if public) | Revenue, growth rate, churn | | Industry reports | Market share estimates |


12-Dimension Scoring Rubric

Score each competitor (and your own product) on a 1-5 scale with evidence notes.

| # | Dimension | 1 (Weak) | 3 (Average) | 5 (Best-in-class) | |---|-----------|----------|-------------|-------------------| | 1 | Features | Core only, many gaps | Solid coverage | Comprehensive + unique capabilities | | 2 | Pricing | Confusing or overpriced | Market-rate, clear | Transparent, flexible, fair | | 3 | UX / Design | Confusing, high friction | Functional, adequate | Delightful, minimal friction | | 4 | Performance | Slow, unreliable | Acceptable | Fast, high uptime, responsive | | 5 | Documentation | Sparse, outdated | Decent coverage | Comprehensive, searchable, with examples | | 6 | Support | Email only, slow response | Chat + email, reasonable SLA | 24/7, multiple channels, fast | | 7 | Integrations | 0-5 native integrations | 6-25 integrations | 26+ or deep ecosystem (API + marketplace) | | 8 | Security | No mentions | SOC2 claimed | SOC2 Type II + ISO 27001 + GDPR | | 9 | Scalability | No enterprise tier | Mid-market ready | Enterprise-grade (SSO, SCIM, SLA) | | 10 | Brand | Generic, unmemorable | Decent positioning | Strong, differentiated, recognized | | 11 | Community | None | Forum or Slack exists | Active, vibrant, user-generated content | | 12 | Innovation | No releases in 6+ months | Quarterly releases | Frequent, meaningful, well-communicated |

Scoring Output Format

| Dimension | Your Product | Competitor A | Competitor B | Competitor C | |-----------|-------------|-------------|-------------|-------------| | Features | 4 | 3 | 5 | 3 | | Pricing | 3 | 4 | 3 | 4 | | ... | ... | ... | ... | ... | | Total (/60) | 38 | 35 | 42 | 33 |


Feature Comparison Matrix

Matrix Structure

| Feature Category | Your Product | Competitor A | Competitor B | Notes | |-----------------|-------------|-------------|-------------|-------| | Core Features | | | | | | Feature 1 | Full | Full | Partial | Comp B lacks [specific capability] | | Feature 2 | Full | Missing | Full | Our differentiator | | Feature 3 | Partial | Full | Full | Gap to close | | Platform | | | | | | Web app | Yes | Yes | Yes | | | iOS app | Yes | No | Yes | Comp A gap | | API access | Full | Limited | Full | | | Enterprise | | | | | | SSO | Yes | No | Yes | | | Audit logs | Yes | Yes | No | | | Custom SLA | Yes | Yes | Yes | |

Score per cell: Full = 5, Partial = 3, Basic = 2, Missing = 0


Pricing Analysis Framework

Pricing Model Comparison

| Attribute | Your Product | Competitor A | Competitor B | |-----------|-------------|-------------|-------------| | Model type | Per seat | Usage-based | Flat rate | | Free tier | Yes (3 users) | Yes (limited) | No | | Entry price | $15/user/mo | $29/mo (up to 1K events) | $49/mo | | Mid-tier price | $35/user/mo | $99/mo | $99/mo | | Enterprise | Custom | Custom | $249/mo | | Annual discount | 20% | 15% | 2 months free | | Trial | 14-day free | 7-day free | 30-day money-back |

Pricing Position Map

| Position | Characteristic | Your Strategy | |----------|---------------|---------------| | Price leader | Lowest price, may signal lower quality | Win on value, not features | | Value leader | Best features-per-dollar ratio | Win on differentiation | | Premium | Highest price, justified by brand/features | Win on exclusivity and support | | Disruptor | Radically different model (free, usage-based) | Win on accessibility |


SWOT Analysis Template

For each competitor, produce:

Competitor SWOT

| Quadrant | Points | |----------|--------| | Strengths (Their advantages) | 3-5 bullets, each anchored to a data signal | | Weaknesses (Their vulnerabilities) | 3-5 bullets, each tied to reviews, missing features, or complaints | | Opportunities for Us | What their weaknesses create for us | | Threats to Us | What their strengths mean for our position |

Evidence rule: Every bullet must cite the data source (review quote, pricing page, job posting count, feature comparison, etc.).


UX Audit Methodology

First-Run Experience Audit

| Dimension | What to Measure | How to Score | |-----------|----------------|--------------| | Time to first value (TTFV) | Minutes from signup to first meaningful output | < 5 min = 5, 5-15 min = 3, > 15 min = 1 | | Steps to activation | Number of screens/actions before core value | < 3 = 5, 3-7 = 3, > 7 = 1 | | Credit card required | Required at signup? | No = 5, Optional = 3, Required = 1 | | Onboarding quality | Wizard, tooltips, empty states | Comprehensive = 5, Basic = 3, None = 1 | | SSO available | Google, Microsoft, etc. | Yes = 5, No = 1 |

Core Workflow Audit

For the 3 most common workflows, compare:

| Workflow | Steps (Yours) | Steps (Competitor) | Friction Points | |----------|-------------|-------------------|-----------------| | [Primary workflow] | N | N | Specific UX issues | | [Secondary workflow] | N | N | Specific UX issues | | [Tertiary workflow] | N | N | Specific UX issues |


Positioning Map

2x2 Positioning Map

Choose the two axes most relevant to your market:

| Common Axis Pairs | When to Use | |-------------------|-------------| | Simple / Complex x Low Price

Truncated for display β€” read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryDevelopment
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

1 medium
competitive-teardown β€” Universal Skill: Install & Safety Check | SkillAgent