competitive-analysis
Skill9 starsChanged 6 months agoMITView on GitHub
Help users understand and respond to competition. Use when someone is positioning against competitors, evaluating market threats, running competitive war games, or deciding how much to focus on competitors versus customers.
54 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- miguelclavel/ux-research-skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- AgnesAI-Labs/agnet-skills-cntheir own version, first seen Nov 1, 2026
- jaskirat1616/grok-skillstheir own version, first seen Nov 1, 2026
- codeApe-7/ai-agent-workflowGrouptheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
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-devSkillusability-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
Dragoon0xSkillonboarding-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
shawnpangSkilllead-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
nicepkgSkilluser-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-skillsSkillemail-marketing
Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics
Also in 3 projects that use this
AnthropicSkilluser-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
Other versions54 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Layneformalized225/ai-cofounder★ 197% same
Wrote their own version · 53
- anthropics/financial-services★ 41ksame name
- anthropics/financial-services-plugins★ 41ksame name
- claude-office-skills/skills★ 433same name
- shawnpang/startup-founder-skills★ 331same name
- mverab/eGEOagents★ 218same name
- Fokkyp/claude-skills★ 211same name
- aakashg/pm-claude-code-setup★ 152same name
- nahid-sparktales/agent-dispatcher★ 59same name
- agencia-conversion/agentic-seo-skills★ 51same name
- launchapp-dev/animus-cli★ 39same name
43 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository78 other files it gives its agents.
- anti-pattern-auditSkill
- brand-storytellingSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- company-intelSkill
- competitor-researchSkill
- composio-cliSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- evening-recapSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-lead-genSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- feedback-trackerSkill
- find-email-by-nameSkill
- focus-keeperSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- github-stars-monitorSkill
- google-calendarSkill
- grafana-monitoringSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- install-openclaw-to-digitaloceanSkill
- install-openclaw-to-hetznerSkill
- install-openclaw-to-ycSkill
- launch-marketingSkill
- lead-enrichmentSkill
- measuring-product-market-fitSkill
- meeting-prepSkill
- metrics-briefingSkill
- morning-briefSkill
- openclaw-guideSkill
- openclaw-user-onboardingSkill
- orthogonalSkill
- outreach-senderSkill
- person-lookupSkill
- ph-launch-timelineSkill
- pipeline-managerSkill
- positioning-messagingSkill
- positioning-workshopSkill
- posthog-analyticsSkill
- prepare-yc-workshopSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- product-led-salesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
- Distinctive: line 9
Follow output preferences from USER.md (language, format, platform constraints).
- Distinctive: line 19
When the user asks for help with competitive analysis:
“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.
Files
[YOUR_PRODUCT] Context
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
Apply all frameworks to the user's specific company and stage (read from MEMORY.md).
Follow output preferences from USER.md (language, format, platform constraints).
For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.
Competitive Analysis
Help the user understand competitive dynamics using frameworks from 49 product leaders who have navigated competition at companies from startups to Netflix and Google.
How to Help
When the user asks for help with competitive analysis:
- Expand the competitive set - Identify not just direct competitors but the status quo and workarounds
- Understand the true threat - Determine if the competition is features, distribution, or fundamental business model
- Find asymmetries - Help them identify unique advantages competitors cannot easily copy
- Design the right response - Balance competitive awareness with customer obsession
Core Principles
Compete against the status quo
April Dunford: "Most folks will discount the status quo, but they shouldn't because in B2B we lose about 40% of our deals to 'no decision,' which actually means we lost to the spreadsheet, we lost to pen and paper." Position specifically against current workarounds, not just competitors.
Define competitive alternatives first
April Dunford: "The first step in a good positioning exercise is to really understand, what do we have to position against? What do I have to beat in order to win a deal?" Look beyond direct competitors to anything customers would do if your product didn't exist.
Understand industry economics deeply
Hamilton Helmer: "Understanding whether or not there is a type of power in place is hard... the hard part is industry economics, what really are the economic relationships." Surface-level competitive analysis misses the structural forces that determine winners.
Ground everything in external reality
Shaun Clowes: "In everything always talk from the customer's perspective, from the market's perspective, from the competitor's perspective. The very small number of PMs do that." Great PMs differentiate by grounding work in market realities, not internal politics.
Include the analog alternative
Bret Taylor: "Why use this instead of Yahoo Yellow Pages? But more than anything else, why use this instead of the Yellow Pages?" Compete against the traditional, non-digital way users solve the problem.
Competition includes workarounds
Jake Knapp: "What's the competition for solving that problem? How do they solve it today? And what are the alternatives? What are the workarounds?" Look beyond direct startup competitors to manual processes and existing habits.
Don't blindly copy competitors
Elena Verna: "Knowing what your competition is doing is extremely important... But blatantly copying all of these best tactics or flows because they're doing better than us - that's where things really go wrong." Use competitors for inspiration, not replication.
Beware competitive myopia
Tanguy Crusson: "Your competitor, if you think of what they do as an iceberg, the top side is what they've shipped in terms of features, but it's based on all this stuff they've built in terms of research." You only see their past output, not their underlying strategy.
Questions to Help Users
- "What would your customer do if your product didn't exist?"
- "What percentage of deals do you lose to 'no decision'?"
- "What's the weakness in your competitor's greatest strength?"
- "Is your advantage in features, distribution, or business model?"
- "How would a competitor describe your positioning?"
- "What market 'current' are you riding or fighting against?"
Common Mistakes to Flag
- Ignoring the status quo - 40% of B2B deals are lost to doing nothing, not to competitors
- Feature-by-feature comparison - Distribution moats often matter more than feature sets
- Fast-following without context - Competitor features reflect year-old thinking, not current strategy
- Assuming data creates moats - Data advantages often diminish once competitors reach scale
- Over-indexing on competitors - Great for market awareness, dangerous for product roadmap
Deep Dive
For all 63 insights from 49 guests, see references/guest-insights.md
Related Skills
- signal-scanner — detects competitor mentions and market signals
- pipeline-manager — competitive intel feeds into prospect scoring
- positioning-workshop — full positioning exercise with competitive research phase
- positioning-messaging — refine messaging based on competitive landscape
- writing-north-star-metrics — metrics to track competitive position
- problem-definition — define the problem you solve differently
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
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.

