Agent skill · Code Review & Quality

competitor-teardown

Structured competitive analysis with feature matrices, SWOT, positioning maps, and UX review. Covers research frameworks, pricing comparison, review mining, and visual deliverables. Use for: market research, competitive intelligence, investor decks, product strategy, sales enablement. Triggers: competitor analysis, competitive analysis, competitor teardown, market research, competitive intelligence, swot analysis, competitor comparison, market landscape, competitor review, competitive landscape, feature comparison, market positioning

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill competitor-teardown --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 10 KB
Bundled scripts: none
Allowed tools: Bash(infsh*)
Path: skills/analysis/competitor-teardown/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Competitor Teardown Structured competitive analysis with research and screenshots via [inference.sh](https://inference.sh) CLI. ## Quick Start > Requires inference.sh CLI (`infsh`). Get installation instructions: `npx skills add inference-sh/skills@agent-tools` ```bash infsh login # Research competitor landscape infsh app run tavily/search-assistant --input '{ "query": "top project management tools comparison 2024 market share" }' # Screenshot competitor's website infsh app run infsh/agent-browser --input '{ "url": "https://competitor.com", "action": "screenshot" }' ``` ## Teardown Framework ### The 7-Layer Analysis | Layer | What to Analyze | Data Source | |-------|----------------|-------------| | 1. **Product** | Features, UX, quality | Screenshots, free trial | | 2. **Pricing** | Plans, pricing model, hidden costs | Pricing page, sales call | | 3. **Positioning** | Messaging, tagline, ICP | Website, ads | | 4. **Traction** | Users, revenue, growth | Web search, press, funding | | 5. **Reviews** | Strengths, weaknesses from users | G2, Capterra, App Store | | 6. **Content** | Blog, social, SEO strategy | Website, social profiles | | 7. **Team** | Size, key hires, background |

What's inside
Steps it walks through
  1. Quick Start
  2. Teardown Framework
  3. The 7-Layer Analysis
  4. Research Commands
  5. Company Overview
  6. Product Analysis
  7. UX Screenshots
  8. Feature Matrix
  9. Structure
  10. Rules
  11. Pricing Comparison
  12. What to Look For
  13. SWOT Analysis
  14. Positioning Map
Ships with 1 file
  • metadata.json
Commands it runs
infsh login
Research competitor landscape
infsh app run tavily/search-assistant --input '{
Screenshot competitor's website
infsh app run infsh/agent-browser --input '{
General intelligence
Funding and financials
infsh app run exa/search --input '{
Recent news
Feature comparison
More from claude-skill-registry
All skills →
About this skill
What does the competitor-teardown skill do?

Structured competitive analysis with feature matrices, SWOT, positioning maps, and UX review. Covers research frameworks, pricing comparison, review mining, and visual deliverables. Use for: market research, competitive intelligence, investor decks, product strategy, sales enablement. Triggers: competitor analysis, competitive analysis, competitor teardown, market research, competitive intelligence, swot analysis, competitor comparison, market landscape, competitor review, competitive landscape, feature comparison, market positioning

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill competitor-teardown --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going