agentleFS
Sign inStart free
aakashgaakashg/pm-claude-code-setup/.claude/skills/competitive-analysis/SKILL.md

competitive-analysis

Skill152 starsChanged 8 months agoMITView on GitHub

What They Built - Core functionality - Target user - Key differentiator What's Smart - 3 decisions they nailed and why What's Weak - 3 gaps or missed opportunities Implications for Us - What to copy, what to avoid, where to differentiate Bad analysis (vague, no evidence): Good analysis (specific, actionable):

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use usability-test-plan, onboarding-flow and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • launchapp-devSkill

    usability-test-plan

    Design a usability test plan with tasks, success metrics, participant criteria, and facilitation guide. Use when planning moderated or unmoderated usability testing sessions.

    Also in 3 projects that use this

  • Dragoon0xSkill

    onboarding-flow

    Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.

    Also in 3 projects that use this

  • shawnpangSkill

    lead-scoring

    When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.

    Also in 3 projects that use this

  • nicepkgSkill

    user-research-synthesis

    Synthesize qualitative and quantitative user research into structured insights and opportunity areas. Use when analyzing interview notes, survey responses, support tickets, or behavioral data to identify themes, build personas, or prioritize opportunities.

    Also in 4 projects that use this

  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 3 projects that use this

  • walternateSkill

    go-to-market

    Build a go-to-market (GTM) strategy for launching a product or entering a new market. Use when planning how to reach customers, position your product, choose channels, set pricing, and execute launch. Covers market entry strategy, customer segmentation, positioning, channel strategy, and GTM execution plan. Trigger on "go-to-market", "GTM strategy", "market entry", "launch strategy", "how to reach customers", "GTM plan".

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Competitive Analysis

Trigger

Activate on "analyze competitor", "competitive analysis", "compare us to [company]".

Behavior

Step 1: Get Context

Ask:

  1. Which competitor?
  2. Which product or feature to analyze?
  3. What's our product for comparison?

Step 2: Analyze

What They Built

  • Core functionality
  • Target user
  • Key differentiator

What's Smart

  • 3 decisions they nailed and why

What's Weak

  • 3 gaps or missed opportunities

Implications for Us

  • What to copy, what to avoid, where to differentiate

Example

Bad analysis (vague, no evidence):

What's Smart:
- They have a good product
- Nice onboarding
- Growing fast

What's Weak:
- Some features are missing
- Could be cheaper

Good analysis (specific, actionable):

What's Smart:
1. Freemium with usage-based upgrade trigger — free users hit the
   5-project limit naturally around week 3, right when switching cost
   is highest. Conversion to paid: ~8% (industry avg: 3-5%).
2. API-first architecture — 400+ integrations in marketplace. This
   creates lock-in that pure UX improvements can't match.
3. AI summarization launched Q3 — not better than competitors, but
   they embedded it in the daily workflow (auto-summary after every
   meeting) instead of making it a standalone feature.

What's Weak:
1. Enterprise pricing is opaque — requires "contact sales" for teams
   over 50. Mid-market buyers (our sweet spot) hate this. Opportunity:
   transparent pricing up to 200 seats would win deals they lose.
2. Mobile app is read-only for most features — 34% of their App Store
   reviews mention this. Their mobile MAU/DAU ratio is 0.3 vs. 0.6 on
   desktop. Opportunity: mobile-first editing.
3. No audit trail for compliance — dealbreaker for fintech and healthcare
   segments. They lose these verticals entirely.

Rules

  • Be specific. "Great UX" is useless. Name the interaction that works and why.
  • Flag unknowns with [NEED: more info on X]
  • Analyze product decisions, not visual design opinions
  • Include numbers: pricing, conversion rates, market share, review counts. Data beats opinion.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free