Framework-driven competitive analysis grounded in market realities, not feature comparison.
Works with
Expands competitive set beyond direct competitors to include status quo, workarounds, and analog alternatives; helps identify the true threat (features, distribution, or business model)
Surfaces structural asymmetries and unique advantages competitors cannot easily copy, with emphasis on grounding analysis in customer and market perspective rather than internal politics
Flags common pitfalls:
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncompetitive-analysisExecute the skills CLI command in your project's root directory to begin installation:
Fetches competitive-analysis from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate competitive-analysis. Access via /competitive-analysis in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
616
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
616
stars
Help the user understand competitive dynamics using frameworks from 49 product leaders who have navigated competition at companies from startups to Netflix and Google.
When the user asks for help with competitive analysis:
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.
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.
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.
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.
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.
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.
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.
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.
For all 63 insights from 49 guests, see references/guest-insights.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend competitive-analysis for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
competitive-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for competitive-analysis matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: competitive-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
competitive-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: competitive-analysis is focused, and the summary matches what you get after install.
competitive-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
competitive-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in competitive-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
competitive-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 67