Guides competitor research for SEO, content, backlinks, and positioning. Use when planning content, auditing articles, building links, or evaluating market position.
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 kostja94/marketing-skills --skill competitor-researchCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncompetitor-researchExecute the skills CLI command in your project's root directory to begin installation:
epx add kostja94/marketing-skills --skill competitor-researchFetches competitor-research from kostja94/marketing-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/competitor-research
Restart Cursor to activate competitor-research. Access via /competitor-researchin 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.
efficient-fable
BuilderIO/skills · productivity · tag: research
deslop
cursor/plugins · Productivity · same category
clean-code-principles
asyrafhussin/agent-skills · Productivity · same category
yt-dlp
lwmxiaobei/yt-dlp-skill · Productivity · same category
framer-motion
pproenca/dot-skills · Productivity · same category
reverse-engineering-tools
gmh5225/awesome-game-security · Productivity · same category
I recommend competitor-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in competitor-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: competitor-research is focused, and the summary matches what you get after install.
competitor-research fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
competitor-research is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: competitor-research is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: competitor-research is focused, and the summary matches what you get after install.
Useful defaults in competitor-research — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for competitor-research matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend competitor-research for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 60