Guides competitor research for SEO, content, backlinks, and positioning. Use when planning content, auditing articles, building links, or evaluating market position.
Works with
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:
Fetches 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:
Restart Cursor to activate competitor-research. Access via /competitor-research 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
2
total installs
2
this week
309
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
309
stars
Guides competitor research for SEO, content, backlinks, and positioning. Use when planning content, auditing articles, building links, or evaluating market position.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
| Type | Purpose | Output |
|---|---|---|
| Keyword/topic | Topics competitors rank for; gaps | Keyword opportunities; content ideas |
| Content | Structure, length, gaps vs top rankers | Length target; H2 structure; content gaps |
| Backlink | Link profile; sites linking to competitors | Link gap; outreach targets |
| Pricing | Competitor pricing, positioning | Pricing context; differentiation |
| SEO metrics | Organic traffic, rankings vs competitors | Benchmark; opportunity areas |
| Method | Practice |
|---|---|
| Reverse engineering | Analyze competitor titles, H1, URL; identify topics they rank for |
| SERP overlap | Keywords with overlapping top-ranking pages → same cluster; #4–10 = opportunity |
| site: operator | site:competitor.com to see indexed pages |
| Tool | Ahrefs, Semrush—competitor keyword overlap, gap analysis |
Output: Keyword opportunities; topics competitors cover that you don't.
| Element | Check |
|---|---|
| Word count | Top 10 average; length target for your content |
| H2 structure | Topics covered; structure to adopt |
| Content gaps | What top rankers cover that you miss |
| Keyword placement | Primary keyword in title, H1, first 100 words |
| Format | Lists, tables, FAQ; match or improve |
Use when: Auditing or creating articles; see article-page-generator for Research Phase integration.
When analyzing or auditing a single article, use this lightweight workflow to obtain competitor articles:
"[target keyword]" to find top-ranking pagesOutput format: Competitor URLs; word count and H2 structure per URL; content gaps vs your article; recommended length target; keyword opportunities (terms top rankers use that your article misses).
| Action | Purpose |
|---|---|
| Compare profiles | Your backlinks vs competitors |
| Link gap | Sites linking to competitors but not you |
| Opportunity | Outreach to those sites; content they might link to |
Tools: Ahrefs, Semrush—Link Intersect, competitor backlink reports. See backlink-analysis.
| Use | Practice |
|---|---|
| Positioning | Where you sit vs competitors |
| Differentiation | Value prop when price differs |
| Alternatives pages | Who to include; how to position |
See pricing-strategy, alternatives-page-generator.
| Source | Use |
|---|---|
| SimilarWeb | Traffic, engagement, traffic sources by domain |
| Ahrefs | Competitor domains, backlinks, DR |
| SEMrush | Organic competitors, traffic share |
| GA | Referral traffic, acquisition by source |
| PostHog | Competitor feature usage (if tracked) |
project-context.md if present| Section | Content |
|---|---|
| Executive Summary | Key findings (top 3), top 3 recommendations |
| Competitor Overview | Competitor, category, market position, key strength |
| Product Comparison | Feature/capability vs Us vs Competitors |
| SWOT Analysis | Our strengths/weaknesses/opportunities/threats; competitor deep dives |
| Marketing & Messaging | Value prop, target audience, key channels |
| Gaps & Opportunities | Gap, opportunity, priority |
| Prioritized Recommendations | Recommendation, impact, effort, owner |
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.
kostja94/marketing-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
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