Startup Design
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
Produce a structured competitive analysis for any product or market.
Install Competitor Teardown
$ npx skills add mohitagw15856/pm-claude-skills --skill competitor-teardown -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/competitor-teardown .claude/skills/competitor-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 "competitor-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-teardown into .claude/skills/competitor-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-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/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-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 mohitagw15856/pm-claude-skills --skill competitor-teardown -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-teardown --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/competitor-teardown .agents/skills/competitor-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 "competitor-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-teardown into .agents/skills/competitor-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-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 mohitagw15856/pm-claude-skills --skill competitor-teardown -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-teardown --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/competitor-teardown .cursor/skills/competitor-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 "competitor-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-teardown into .cursor/skills/competitor-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-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/mohitagw15856/pm-claude-skills.git --path skills/competitor-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 mohitagw15856/pm-claude-skills --skill competitor-teardown -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills competitor-teardown --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/competitor-teardown .gemini/skills/competitor-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 "competitor-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-teardown into .gemini/skills/competitor-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-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 mohitagw15856/pm-claude-skills competitor-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 mohitagw15856/pm-claude-skills --skill competitor-teardown -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/competitor-teardown .github/skills/competitor-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 "competitor-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-teardown into .github/skills/competitor-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-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 mohitagw15856/pm-claude-skills --skill competitor-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 mohitagw15856/pm-claude-skills competitor-teardown --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/competitor-teardown .opencode/skills/competitor-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 "competitor-teardown" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/competitor-teardown into .opencode/skills/competitor-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-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
competitor-teardown- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 696 words
- Files
- 4 (incl. references)
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Produce a structured competitive analysis for any product or market.
- Works in 6 steps: Competitive Landscape Overview → Positioning Map → Feature Comparison Table → …
- Asked for a competitor analysis
- SKILL.md covers Required Inputs, Deeper Materials, Output Structure and Scoring Rubric (0–40), plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Competitor Teardown is an agent skill from mohitagw15856/pm-claude-skills. Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations. For a full landscape doc with feature matrix and win/loss analysis use competitive-analysis instead.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/intel-sourcing-guide.md`, `references/worked-example.md` and `templates/teardown-skeleton.md`).
It sits in Marketing & SEO, covering Competitor analysis, Positioning and messaging and Startup and business strategy. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked for a competitor analysis
- Competitive teardown
- Market comparison
- Positioning map
Example prompts
- “/competitor-teardown”
Workflow steps
6 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 1cbf1f0. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Competitor Teardown loads about 1.4k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 696 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 696 words, ~1,437 tokens.
Download SKILL.mdSave it as
.claude/skills/competitor-teardown/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- competitor-teardown
- description
- Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations. For a full landscape doc with feature matrix and win/loss analysis use competitive-analysis instead.
Competitor Teardown Skill
This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.
Required Inputs
Ask the user for these if not provided:
- Your product (name + one-line description)
- Competitors to analyse (list 2–5 names; if not provided, ask)
- Analysis depth (quick overview / detailed teardown)
- Primary use case for this analysis (e.g. sales enablement, investor deck, internal strategy, product planning)
Deeper Materials
references/intel-sourcing-guide.md— where competitive facts come from (four source tiers), which source to use per teardown section, the [verified]/[reported]/[assumed] confidence labels, and the ethics line. Apply its labelling to every substantive claim in the output.templates/teardown-skeleton.md— a fill-in teardown with the confidence labels and a verification queue built in. Offer it when the user wants to gather the intel themselves.
Output Structure
1. Competitive Landscape Overview
One paragraph summarising the market dynamic: who the key players are, how the market is segmented, and where the white space sits. Keep this under 150 words — it's the exec summary.
2. Positioning Map
Describe a 2x2 positioning map in text form (since you can't render images):
- Define the two axes relevant to this market (e.g. "Ease of Use vs. Depth of Features" or "Price vs. Enterprise Readiness")
- Place each competitor in one quadrant with a one-sentence rationale
- Place the user's product and highlight the strategic implication
3. Feature Comparison Table
| Feature / Capability | [Your Product] | [Competitor A] | [Competitor B] | [Competitor C] |
|---|---|---|---|---|
| [Feature] | ✅ / ❌ / 🟡 Partial |
Use ✅ (has it), ❌ (doesn't have it), 🟡 (partial/limited). Add a "Strategic Notes" column for features where the difference is a significant selling point or risk.
Include 10–15 rows. If user hasn't provided feature details, note which cells need to be verified.
4. Messaging Analysis
For each competitor, analyse their public-facing messaging (website headline, tagline, primary value prop):
[Competitor Name]
- Their primary claim: [what they say they do]
- Target audience signal: [who they seem to be targeting based on language/imagery]
- Emotional hook: [fear / aspiration / authority / speed / simplicity]
- Gap or weakness in their messaging: [what they don't address that your product could own]
5. SWOT Summary
Produce a clean SWOT for the user's product in the context of this competitive landscape:
- Strengths: [2–3 genuine differentiators]
- Weaknesses: [2–3 honest gaps or vulnerabilities]
- Opportunities: [2–3 market gaps or competitor weaknesses to exploit]
- Threats: [2–3 competitor moves or market shifts to watch]
6. Strategic Recommendations
3–5 actionable recommendations based on the analysis. Frame each as: "Given [observation], [your product] should [action] to [outcome]."
Show full SKILL.md (288 more words)Show less
Scoring Rubric (0–40)
Score any output of this skill before handing it over; 32+ is ship-quality.
| Dimension | 0 | 5 | 10 |
|---|---|---|---|
| Map meaningfulness | Axes are generic (price × quality) | Market-specific axes but positions unjustified | Axes capture the real buying tension in this market and every placement is defensible |
| Comparative depth | Feature table is checkmarks | Features compared with some notes | Differentiators carry strategic notes explaining why the gap matters and to whom |
| SWOT honesty | Weaknesses/threats softened to niceties | Honest but unprioritized | Weaknesses and threats stated plainly, ranked by how much they should worry you |
| Recommendation specificity | Generic strategy advice | Actionable but unlinked to findings | Each recommendation follows "given [observation], do [action] to [outcome]" and traces to the analysis |
Quality Checks
- Axes on positioning map are meaningful and specific to this market
- Feature table includes strategic notes on key differentiators
- Messaging analysis covers all named competitors
- SWOT is honest — Weaknesses and Threats should not be softened
- Recommendations are specific and actionable, not generic strategy advice
Anti-Patterns
- Do not mark feature presence as equivalent across competitors without noting quality differences — both products may have "reporting" while one's is meaningfully better
- Do not position the user's product in the most favourable quadrant without justification — a self-serving positioning map that ignores real competitive pressure provides no strategic value
- Do not soften Weaknesses or Threats in the SWOT — a SWOT that only celebrates strengths is a marketing document, not a strategy tool
- Do not include unverifiable claims about competitor capabilities without flagging them as assumptions — presenting rumours as facts damages analytical credibility
Example Trigger Phrases
- "Do a competitor analysis of [Product] vs [Competitor A] and [Competitor B]"
- "Tear down [Competitor]'s positioning"
- "Give me a competitive landscape for [market]"
- "Build a SWOT for our product against [competitor]"
© mohitagw15856, 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 (references) in skills/competitor-teardown of mohitagw15856/pm-claude-skills.
- SKILL.md
- references/intel-sourcing-guide.md
- references/worked-example.md
- templates/teardown-skeleton.md
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Competitor 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 |
|---|---|---|---|---|---|---|
| Competitor Teardown this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Cashclaw Competitor Analyzerertugrulakben/cashclaw | 303 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Competitive Teardownalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| 08 Competitor Research Globalminhnv0807/ai-business-skills | 609 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Competitor Analysissocial-media-skills/skills | 134 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Cashclaw Competitor Analyzer
ertugrulakben/cashclaw
Performs competitor research and generates detailed analysis reports with market positioning insights.
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.
08 Competitor Research Global
minhnv0807/ai-business-skills
A skill your agent uses when the user needs to understand competitors — direct, indirect, and substitute tiers, positioning map, SWOT, ad and content benchmark, pricing comparison, and the market…
Competitor Analysis
social-media-skills/skills
Competitor analysis for social media — public-data competitive reconnaissance to find the gap a brand can own.
Competitor Teardown
irinabuht12-oss/marketing-skills
Systematic competitive analysis covering positioning, messaging hierarchy, objection handling, and CTA strategy from landing page URLs or screenshots.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Competitor Teardown
What does Competitor Teardown do?
Produce a structured competitive analysis for any product or market. Competitor Teardown is an agent skill from mohitagw15856/pm-claude-skills. Produce a structured competitive analysis for any product or market.
When should I use Competitor Teardown?
Competitor Teardown fits situations like: asked for a competitor analysis; competitive teardown; market comparison; positioning map.
How do I install Competitor Teardown in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill competitor-teardown -a claude-code`. Or copy the skill folder (skills/competitor-teardown in mohitagw15856/pm-claude-skills) into .claude/skills/competitor-teardown in your project. Claude Code loads it when a task matches its description.
How do I install Competitor Teardown in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill competitor-teardown -a codex`. Or copy the skill folder (skills/competitor-teardown in mohitagw15856/pm-claude-skills) into .agents/skills/competitor-teardown in your project. Codex loads it when a task matches its description.
Can I use Competitor 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 mohitagw15856/pm-claude-skills --skill competitor-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/competitor-teardown, .gemini/skills/competitor-teardown, .github/skills/competitor-teardown and .opencode/skills/competitor-teardown in your project.
What does Competitor Teardown need to run?
SKILL.md names no scripts, command-line tools or credentials: Competitor Teardown is instructions for the agent only.
Does Competitor 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 Competitor 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. Review the folder before installing.
What licence does Competitor Teardown use?
Competitor Teardown is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Competitor Teardown use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.
What are the alternatives to Competitor Teardown?
Skills that share tags, products or a category with Competitor Teardown: Startup Design (ferdinandobons/startup-skill, 1.2k stars), Cashclaw Competitor Analyzer (ertugrulakben/cashclaw, 303 stars), Competitive Teardown (alirezarezvani/claude-skills, 28k stars) and 08 Competitor Research Global (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Competitor Teardown?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-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.