Amazon Competitor Monitoring
nexscope-ai/Amazon-Skills
Amazon competitor monitoring and competitive intelligence for sellers.
Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action…
Install Competitive Teardown
$ npx skills add borghei/Claude-Skills --skill competitive-teardown -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills competitive-teardown --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/business-growth/competitive-teardown .claude/skills/competitive-teardown && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "competitive-teardown" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/competitive-teardown into .claude/skills/competitive-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitive-teardown", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/business-growth/competitive-teardownType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill competitive-teardown -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills competitive-teardown --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/business-growth/competitive-teardown .agents/skills/competitive-teardown && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "competitive-teardown" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/competitive-teardown into .agents/skills/competitive-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitive-teardown", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill competitive-teardown -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills competitive-teardown --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/business-growth/competitive-teardown .cursor/skills/competitive-teardown && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "competitive-teardown" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/competitive-teardown into .cursor/skills/competitive-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitive-teardown", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path business-growth/competitive-teardown--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill competitive-teardown -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills competitive-teardown --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/business-growth/competitive-teardown .gemini/skills/competitive-teardown && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "competitive-teardown" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/competitive-teardown into .gemini/skills/competitive-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitive-teardown", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills competitive-teardownInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill competitive-teardown -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/business-growth/competitive-teardown .github/skills/competitive-teardown && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "competitive-teardown" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/competitive-teardown into .github/skills/competitive-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitive-teardown", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill competitive-teardown -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills competitive-teardown --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/business-growth/competitive-teardown .opencode/skills/competitive-teardown && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "competitive-teardown" agent skill from https://github.com/borghei/Claude-Skills/tree/main/business-growth/competitive-teardown into .opencode/skills/competitive-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitive-teardown", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
competitive-teardown- GitHub stars
- 886
- Token cost
- ~5.4k tokens
- SKILL.md length
- 2,206 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 354
- Repo updated
- First seen
- Licence
- MIT
At a glance
Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action…
- Works in 3 steps: competitor_scorer.py → feature_matrix_builder.py → battle_card_generator.py
- Tasks that involve Quizzes and assessments
- SKILL.md covers Table of Contents, When to Use, Clarify First and Teardown Workflow, plus 8 more sections
- Runs Python scripts from its folder; calls python
What it does
Competitive Teardown is an agent skill from borghei/Claude-Skills. 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.
Its SKILL.md is about 5.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/battle_card_generator.py`, `scripts/competitor_scorer.py` and `scripts/feature_matrix_builder.py`).
It sits in Education, covering Quizzes and assessments, Startup and business strategy and Competitor analysis. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Tasks that involve Quizzes and assessments
- Tasks that involve Startup and business strategy
- Tasks that involve Competitor analysis
Example prompts
- “/competitive-teardown”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Competitive Teardown loads about 5.4k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 2,206 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,206 words, ~5,379 tokens.
Download SKILL.mdSave it as
.claude/skills/competitive-teardown/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- 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
- metadata.author
- borghei
- metadata.category
- business-growth
- metadata.updated
- 2026-03-31
- metadata.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
- Teardown Workflow
- Data Collection Framework
- 12-Dimension Scoring Rubric
- Feature Comparison Matrix
- Pricing Analysis Framework
- SWOT Analysis Template
- UX Audit Methodology
- Positioning Map
- Action Plan Framework
- Battle Card Template
- Stakeholder Presentation
- Output Artifacts
- Related Skills
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
- Define competitors -- List 2-4 competitors. Confirm which is the primary focus.
- Collect data -- Gather intelligence from at least 3 of the 6 sources per competitor.
- Score using rubric -- Apply the 12-dimension rubric to produce a numeric scorecard.
- Generate comparison outputs -- Feature matrix, pricing analysis, SWOT, positioning map.
- Build action plan -- Translate findings into quick wins, medium-term, and strategic priorities.
- 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 |
| Honest reviews, comparison threads | |
| 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 |
| 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 / High Price | General product comparison |
| SMB / Enterprise x Narrow / Broad Features | Market segment analysis |
| Self-Serve / Sales-Led x Point Solution / Platform | Go-to-market comparison |
| Technical / Non-Technical x Niche / Horizontal | Audience analysis |
Show full SKILL.md (878 more words)Show less
Map Template
High Price / Enterprise
│
│
[Competitor B] │ [Competitor C]
│
Simple ─────────────────┼─────────────────── Complex
│
[YOUR PRODUCT] │ [Competitor A]
│
│
Low Price / SMBAction Plan Framework
Three Horizons
| Horizon | Timeframe | Effort | Examples |
|---|---|---|---|
| Quick wins | 0-4 weeks | Low | Publish comparison pages, update pricing page, add missing trust badges |
| Medium-term | 1-3 months | Moderate | Build top-requested integration, improve onboarding TTFV, launch free tier |
| Strategic | 3-12 months | High | Enter new market segment, build API v2, achieve SOC2 Type II |
Priority Scoring
For each action item, score:
| Factor | Weight | Scale |
|---|---|---|
| Competitive impact | 40% | How much does this close or widen a gap? |
| Customer demand | 30% | How many customers/prospects request this? |
| Implementation effort | 20% | How hard is this to build/execute? |
| Revenue impact | 10% | Direct revenue contribution? |
Battle Card Template
One-Page Battle Card
COMPETITOR: [Name]
LAST UPDATED: [Date]
THREAT LEVEL: [LOW / MEDIUM / HIGH / CRITICAL]
THEIR POSITIONING: [1 sentence]
OUR POSITIONING AGAINST THEM: [1 sentence]
WHERE THEY WIN:
- [Strength 1 with evidence]
- [Strength 2 with evidence]
- [Strength 3 with evidence]
WHERE WE WIN:
- [Advantage 1 with evidence]
- [Advantage 2 with evidence]
- [Advantage 3 with evidence]
LANDMINES (questions that expose their weaknesses):
- "How does [competitor] handle [weakness area]?"
- "Can you show me [feature they lack]?"
- "What do their customers say about [common complaint]?"
OBJECTION HANDLING:
- "They're cheaper" → [Response with value framing]
- "They have [feature]" → [Response with alternative/roadmap]
- "Everyone uses them" → [Response with differentiation]
PRICING COMPARISON:
[Quick comparison table]
CUSTOMER QUOTE:
"[Quote from a customer who switched from this competitor to you]"Stakeholder Presentation
7-Slide Structure
| Slide | Content |
|---|---|
| 1. Executive Summary | Threat level, top strength, top opportunity, recommended action |
| 2. Market Position | 2x2 positioning map with all players |
| 3. Feature Scorecard | 12-dimension scores, total comparison |
| 4. Pricing Analysis | Pricing comparison table + key pricing insight |
| 5. UX Comparison | Where they win (3 bullets) vs where we win (3 bullets) |
| 6. Voice of Customer | Top 3 competitor complaints from reviews (quoted) |
| 7. Action Plan | Quick wins, medium-term, strategic priorities |
Output Artifacts
| Artifact | Format | Description |
|---|---|---|
| Data Collection Report | Structured notes per source | Raw intelligence organized by source type |
| 12-Dimension Scorecard | Scored table with evidence | Numeric comparison across all dimensions |
| Feature Comparison Matrix | Grid table | Feature-by-feature comparison with scoring |
| Pricing Analysis | Comparison table + position map | Model comparison, tier mapping, positioning |
| SWOT Analysis | Per-competitor 4-quadrant | Anchored to data signals |
| UX Audit | Scored checklist | TTFV, steps, friction analysis |
| Positioning Map | 2x2 diagram | Visual market position |
| Action Plan | Three-horizon table | Prioritized competitive responses |
| Battle Card | One-page template | Sales-ready competitive reference |
| Stakeholder Presentation | 7-slide outline | Executive-ready competitive briefing |
Related Skills
- competitor-alternatives -- Use for creating comparison and alternative pages for SEO/marketing. Competitive-teardown provides the intelligence; competitor-alternatives produces the marketing content.
- pricing-strategy -- Use when competitive analysis reveals pricing misalignment. Feed teardown pricing data into pricing-strategy.
- page-cro -- Use for optimizing your comparison or competitor landing pages for conversion.
- content-creator -- Use for writing competitive content (blog posts, comparison guides) based on teardown findings.
Tool Reference
1. competitor_scorer.py
Purpose: Score competitors across the 12-dimension rubric and generate a numeric comparison scorecard.
python scripts/competitor_scorer.py competitor_data.json
python scripts/competitor_scorer.py competitor_data.json --json| Flag | Required | Description |
|---|---|---|
competitor_data.json | Yes | JSON file with competitor dimension scores and evidence |
--json | No | Output results as JSON |
--weights | No | Custom dimension weights as JSON string (default: equal weights) |
2. feature_matrix_builder.py
Purpose: Build a feature comparison matrix from structured feature data and calculate coverage scores.
python scripts/feature_matrix_builder.py features.json
python scripts/feature_matrix_builder.py features.json --json| Flag | Required | Description |
|---|---|---|
features.json | Yes | JSON file with feature comparison data |
--json | No | Output results as JSON |
3. battle_card_generator.py
Purpose: Generate a one-page battle card from competitor data for sales team use.
python scripts/battle_card_generator.py competitor_profile.json
python scripts/battle_card_generator.py competitor_profile.json --json| Flag | Required | Description |
|---|---|---|
competitor_profile.json | Yes | JSON file with competitor profile data |
--json | No | Output results as JSON |
--format | No | Output format: text (default) or markdown |
Troubleshooting
| Problem | Likely Cause | Solution |
|---|---|---|
| Scoring feels subjective across analysts | No shared rubric calibration | Use the 12-dimension rubric with explicit 1/3/5 definitions; have two analysts score independently and reconcile |
| Data is stale within weeks of teardown | Fast-moving competitors | Set calendar reminders for monthly pricing checks and quarterly full refreshes; use competitor_scorer.py to track score changes over time |
| Feature matrix has too many rows to be useful | Trying to capture every micro-feature | Group features into 8-12 categories; detail only the top differentiators |
| Battle cards are not used by sales | Too long, too academic, or not actionable | Keep to one page; lead with "Where We Win" and "Landmines"; validate with 3 sales reps before distributing |
| Review data is contradictory | Small sample size or selection bias | Target 50+ reviews per competitor across G2, Capterra, and TrustRadius; weight recent reviews more heavily |
| Cannot get pricing data for enterprise tiers | Custom pricing not published | Use sales intel (request a demo), G2 pricing data, or customer interviews for directional estimates |
| SWOT analysis has no actionable output | Analysis lacks connection to action plan | Every SWOT bullet must map to a specific quick-win, medium-term, or strategic action |
Success Criteria
- 12-dimension scorecard completed with evidence notes for every score
- Feature matrix covers at least 80% of features that prospects evaluate
- Battle cards reviewed and approved by 3+ sales representatives
- Pricing data verified within the last 30 days
- Teardown produces at least 3 actionable quick wins and 2 strategic priorities
- Stakeholder presentation reviewed and feedback incorporated within 1 week
- Teardown data refreshed quarterly with score trend tracking
Scope & Limitations
- In scope: Product analysis, feature comparison, pricing deconstruction, UX audit, SWOT analysis, battle card creation, action plan generation
- Out of scope: Primary market research (customer interviews, surveys), financial modeling, legal competitive analysis, intellectual property assessment
- Data dependency: Quality depends on publicly available data, user reviews, and product access; some competitors may have limited public information
- Bias risk: Teardowns conducted by internal teams may have confirmation bias; consider external validation for high-stakes decisions
- Point-in-time: Teardowns are snapshots; competitors evolve continuously -- schedule regular refreshes
Integration Points
- competitor-alternatives -- Teardown provides the data; competitor-alternatives produces the marketing content (comparison and alternative pages)
- pricing-strategy -- When teardown reveals pricing misalignment, feed pricing data into pricing-strategy for repositioning analysis
- page-cro -- Use for optimizing your comparison or competitor landing pages for conversion after teardown produces the content
- sales-engineer -- Battle cards feed directly into sales engineering competitive positioning and RFP responses
- customer-success-manager -- When exit surveys reveal COMPETITOR as a top churn reason, use teardown data to understand what competitors offer that you do not
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in business-growth/competitive-teardown of borghei/Claude-Skills.
- SKILL.md
- scripts/battle_card_generator.py
- scripts/competitor_scorer.py
- scripts/feature_matrix_builder.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Competitive Teardown next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Competitive Teardown this skillborghei/Claude-Skills | 886 | — | ~5.4k | Automated safety check: Pass | MIT | |
| Amazon Competitor Monitoringnexscope-ai/Amazon-Skills | 741 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Competitive Teardownalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Competitor Comparison Matrixfirecrawl/web-agent | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Market Research Analysismanojbajaj95/claude-gtm-plugin | 105 | — | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Competitive Teardown
alirezarezvani/claude-skills
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.
Competitor Comparison Matrix
firecrawl/web-agent
Compares two or more products or companies on pricing, features and positioning by scraping their sites, and returns a normalized JSON matrix.
Startup Design
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
Market Research Analysis
manojbajaj95/claude-gtm-plugin
Comprehensive market research and analysis skill. An agent skill from manojbajaj95/claude-gtm-plugin.
Sellersprite Amazon Research
liangdabiao/amazon-sorftime-research-MCP-skill
卖家精灵 Amazon 全链路数据调研 Skill。通过 43 个 MCP 数据工具完成选品分析、关键词研究、竞品监控、市场分析、定价策略、评论分析、广告优化、流量分析、Listing 优化和蓝海机会挖掘。触发场景：(1) 用户询问 Amazon 选品/市场/竞品分析 (2) 用户输入 /product-research, /market-analysis…
More from borghei/Claude-Skills
All 354 skills in this repoAgent Harness
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
Agents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Related
Categories
Questions about Competitive Teardown
What does Competitive Teardown do?
Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action…. Competitive Teardown is an agent skill from borghei/Claude-Skills. 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.
When should I use Competitive Teardown?
Competitive Teardown fits situations like: tasks that involve Quizzes and assessments; tasks that involve Startup and business strategy; tasks that involve Competitor analysis.
How do I install Competitive Teardown in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill competitive-teardown -a claude-code`. Or copy the skill folder (business-growth/competitive-teardown in borghei/Claude-Skills) into .claude/skills/competitive-teardown in your project. Claude Code loads it when a task matches its description.
How do I install Competitive Teardown in Codex?
Run `npx skills add borghei/Claude-Skills --skill competitive-teardown -a codex`. Or copy the skill folder (business-growth/competitive-teardown in borghei/Claude-Skills) into .agents/skills/competitive-teardown in your project. Codex loads it when a task matches its description.
Can I use Competitive Teardown in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill competitive-teardown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/competitive-teardown, .gemini/skills/competitive-teardown, .github/skills/competitive-teardown and .opencode/skills/competitive-teardown in your project.
What does Competitive Teardown need to run?
Going by SKILL.md and its folder, Competitive Teardown needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Competitive Teardown access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Competitive Teardown safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Competitive Teardown use?
Competitive Teardown is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Competitive Teardown use?
About 5.4k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Competitive Teardown?
Skills that share tags, products or a category with Competitive Teardown: Amazon Competitor Monitoring (nexscope-ai/Amazon-Skills, 741 stars), Competitive Teardown (alirezarezvani/claude-skills, 28k stars), Competitor Comparison Matrix (firecrawl/web-agent, 1.2k stars) and Startup Design (ferdinandobons/startup-skill, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Competitive Teardown?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.