Framework-driven competitive analysis grounded in market realities, not feature comparison.
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
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
Submit your Claude Code skill and start earning
epx add refoundai/lenny-skills --skill competitive-analysisCompatible with
Supported agents
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:
epx add refoundai/lenny-skills --skill competitive-analysisFetches 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:
.cursor/skills/competitive-analysis
Restart Cursor to activate competitive-analysis. Access via /competitive-analysisin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
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.
premortem
parcadei/continuous-claude-v3 · Productivity · same category
framer-motion
pproenca/dot-skills · Productivity · same category
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
xauusd-trading
huynguyen03dev/xauusd-trading · Productivity · same category
smart-ocr
claude-office-skills/skills · Productivity · same category
sports-betting-analyzer
onewave-ai/claude-skills · Productivity · same category
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