Skip to content
cccskills
FreePublished on GitHub

competitive-teardown

Deep competitor analysis. Tear apart a specific competitor or compare multiple competitors. Use when the user names a competitor or asks "who else is doing this?"

The English summary is being prepared. Showing the original description.

Works withReddit
See how to install

Files included (2)

  • SKILL.md2.9 KB
  • example-analysis.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Competitive Teardown

Study competitors like you're planning to beat them.

When to Use

  • User names a specific competitor
  • "Who else is doing this?"
  • Before building, to find gaps
  • Preparing for investor "competition slide"

See example-analysis.md for a filled-in competitor teardown showing the format and depth expected.

Single Competitor Teardown

Product

  • What do they actually do? (use the product, not just the landing page)
  • Key features
  • What's good about it
  • What sucks (check 1-star reviews on App Store, G2, Reddit)
  • Pricing tiers

Business

  • Funding (Crunchbase, PitchBook)
  • Revenue if known (press, SimilarWeb traffic guesses)
  • Team size (LinkedIn)
  • Founded when
  • Growth signals (hiring? launching new features? going quiet?)

Users

  • Who uses it? (check case studies, reviews, social mentions)
  • How do they get users? (SEO, ads, viral, sales team)
  • Community size (Discord, Reddit, Twitter followers)
  • NPS or satisfaction signals

Weaknesses

  • Negative reviews (patterns, not one-offs)
  • Missing features users ask for
  • Pricing complaints
  • Technical limitations
  • Support complaints

Multi-Competitor Comparison

Create a table:

Competitor ACompetitor BCompetitor CUs (planned)
One-liner
Target user
Key feature
Pricing
Funding
Weakness
Our advantage

Find the Gap

After analysis, answer:

  • Where are ALL competitors weak?
  • What do users want that nobody does well?
  • Is there an underserved segment?
  • What positioning would make us different?

Rules

  • Use the product. Don't just read the landing page.
  • Check reviews on multiple platforms
  • Look for patterns in complaints, not single reviews
  • Be fair. Give credit where it's due.
  • If a competitor is way ahead, say so. Don't hide it.

Gotchas

  • Don't just read the landing page. Sign up for free trials. Watch demo videos. Read user forums. The landing page is marketing, not the product.
  • One-star reviews are gold, but look for patterns. A single angry review means nothing. Ten people saying the same thing is a signal.
  • Funding ≠ success. A competitor with $50M raised and no revenue is weaker than one with $2M raised and growing 20% monthly.
  • Don't confuse features with moat. A feature can be copied in a sprint. Distribution, data, and network effects can't.
  • Check if they're growing or coasting. Recent job postings, new features, blog activity — these signal momentum. Silence signals trouble.

Output

Save to the project's 02-research/ folder. Use the template from templates/competitor-analysis.md if it fits.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Creates RPC-style endpoint following layered architecture (Controller → Manager → Repository). Use when creating new API endpoints or CRUD operations.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

Write blog posts, guides, tutorials, and long-form content. Sounds like a real person, not AI. Use when the user wants polished written content.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

Design RPC-style APIs with layered architecture (Controller → Manager → Repository). Use when creating new API endpoints, designing API contracts, or reviewing API patterns.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

Run a structured brainstorm session for startup ideas. Takes a theme or problem and generates ideas with quick gut-checks. Use when the user wants to explore a space or generate new ideas.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

Run real browser QA with Playwright. Use when testing a frontend feature, verifying UI before PR, smoke testing after deploy, or investigating reported visual bugs.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

CI/CD pipeline patterns for GitHub Actions, PR automation, and deployment workflows. Use when setting up CI, fixing broken pipelines, automating PR checks, or configuring deployment.

The English summary is being prepared. Showing the original description.

c0x12c/ai-toolkit109Updated Jun 18, 2026

See all skills by c0x12c

Report a problem with this skill