agentleFS
adhyayanrathi01adhyayanrathi01/product-manager-os/skills/competition/competitive-analysis/SKILL.md

competitive-analysis

Skill2 starsChanged 2 months agoMITView on GitHub

Research competitors, substitutes, adjacent products, and the status quo to support product strategy and prioritization. Use for feature comparisons, positioning, market gaps, switching behavior, pricing context, and understanding how users solve the job today.

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 10 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

  • AnthropicSkill

    user-research

    Plan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify that current primary sources are accessible.

    line 12
  2. Distinctive:

    If current evidence is unavailable, return a partial research plan rather than a capability or pricing conclusion.

    line 13
  3. Distinctive:

    import and migration paths

    line 25
  4. Distinctive:

    Add marketing, sales, or company-finance dimensions only when asked.

    line 29
  5. Very specific:

    Search for "alternatives to <product>", the precise category, and "<product> vs" comparison pages.

    line 32
  6. Distinctive:

    Wait for the PM to confirm the list.

    line 35
  7. Distinctive:

    Every cell except unknown cites a source.

    line 41
  8. Distinctive:

    Use one as-of date for the whole comparison.

    line 43
  9. Distinctive:

    When public evidence is thin, narrow the comparison to what the evidence supports.

    line 44
  10. Distinctive:

    Treat a documented lack of public information as a finding.

    line 46
  11. Distinctive:

    Never estimate headcount or funding without a source.

    line 47
  12. Distinctive:

    Never declare a winner, rank options, or score threats, whoever is asking.

    line 55
  13. Very specific:

    Every field above must appear as a labeled section in the produced output.

    line 64

“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Competitive Analysis

<!-- CORE:BEGIN -->

Contract

  • Require the PM decision, user job, market boundary, alternatives, comparison dimensions, geography when relevant, and observation date.
  • Verify that current primary sources are accessible. Mark unverifiable, stale, paywalled, or inferred claims explicitly.
  • If current evidence is unavailable, return a partial research plan rather than a capability or pricing conclusion.
  • Emit the shared evidence handoff when findings feed a project workflow.
<!-- CORE:END -->

Process

  1. Define the PM decision, target user, user job, market boundary, and comparison dimensions.
    • For a product manager, the default dimensions are:
      • the user job and its workflow steps
      • target segment
      • onboarding and time to first value as described
      • pricing and plan gates
      • import and migration paths
      • integrations
      • status quo and workarounds
      • release pace
    • Add marketing, sales, or company-finance dimensions only when asked.
  2. Include direct competitors, substitutes, internal workarounds, and doing nothing where relevant.
  3. Profile any alternatives the user named now. Discover the rest before profiling them, following skills/evidence/public-research-method.md from the first search.
    • Search for "alternatives to <product>", the precise category, and "<product> vs" comparison pages.
    • Propose at most 5. Type each as direct, adjacent, substitute, or status quo, with a reason and a URL.
    • List misfits in an "unknown" bucket with a reason.
    • Wait for the PM to confirm the list. The output at this pause still includes every required field, with the proposed list under Questions for the PM.
  4. Gather evidence with skills/evidence/public-research-method.md. Prefer current primary sources for product capabilities, pricing, policies, and positioning. Record the method's stop verdict under Gaps.
  5. Record the source and observation date.
  6. Separate verified facts from interpretation and inference. For each alternative, state what it claims and what is confirmed.
  7. Profile every alternative with the same template so profiles compare.
  8. Fill each comparison cell with yes, no, partial, unknown, or n/a.
    • Every cell except unknown cites a source.
    • Mark "no" only when a first-party page states the absence. When pages are silent, mark unknown and write "not observed on [pages], as of [date]".
    • Use one as-of date for the whole comparison.
  9. When public evidence is thin, narrow the comparison to what the evidence supports.
    • Name the smallest gaps and how to close each one.
    • Treat a documented lack of public information as a finding.
    • Never estimate headcount or funding without a source.
  10. On a rerun, report what changed first: then, now, and confidence.
  11. List leadership only as announced roles.
  12. Compare workflows and outcomes, not only feature checklists.
  13. Identify parity expectations, meaningful differentiation, underserved needs, and trade-offs.
  14. Connect findings to existing customer and product evidence.
  15. Present strategic options and questions for the PM.

Never declare a winner, rank options, or score threats, whoever is asking. Produce battlecards or talk tracks only when the user asks for them.

<!-- CORE:BEGIN -->

Output

Provide source coverage and dates, verified comparisons, inferred implications, gaps, trade-offs, questions for the PM, and a shared evidence packet when the work feeds a project.

Required fields: Source coverage and dates|Verified comparisons|Inferred implications|Gaps|Trade-offs|Questions for the PM

Every field above must appear as a labeled section in the produced output. Verify with evals/check-output.sh competitive-analysis <artifact>.

<!-- CORE:END -->

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.