If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncompetitive-briefExecute the skills CLI command in your project's root directory to begin installation:
Fetches competitive-brief from anthropics/knowledge-work-plugins 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-brief. Access via /competitive-brief 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
0
total installs
0
this week
11.0K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
11.0K
stars
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Research competitors and generate a structured competitive analysis comparing positioning, messaging, content strategy, and market presence.
User runs /competitive-brief or asks for a competitive analysis, competitor research, or market comparison.
Gather the following from the user:
Competitor name(s) — one or more competitors to analyze (required)
Your company/product context (optional but recommended):
Focus areas (optional — if not specified, cover all):
For each competitor, research using web search:
Gather intelligence from these categories of sources:
For each competitor:
| Dimension | Your Company | Competitor A | Competitor B |
|---|---|---|---|
| Primary tagline | ... | ... | ... |
| Target buyer | ... | ... | ... |
| Key differentiator | ... | ... | ... |
| Tone/voice | ... | ... | ... |
| Core value prop | ... | ... | ... |
(Include user's company only if they provided their positioning context)
For each competitor, document:
Identify each competitor's story arc:
This reveals positioning strategy and emotional appeals.
For each competitor's messaging, assess:
Map content across competitors by:
| Topic/Theme | Your Content | Competitor A | Competitor B | Gap? |
|---|---|---|---|---|
| [Topic 1] | Blog post, ebook | Blog series, webinar | Nothing | Opportunity for B |
| [Topic 2] | Nothing | Whitepaper | Blog post, video | Gap for you |
| [Topic 3] | Case study | Nothing | Case study | Parity |
| Content Format | You | Comp A | Comp B | Comp C |
|---|---|---|---|---|
| Blog posts | Y | Y | Y | Y |
| Case studies | Y | Y | N | Y |
| Ebooks/Whitepapers | N | Y | Y | N |
| Webinars | Y | Y | Y | N |
| Podcast | N | N | Y | N |
| Video content | N | Y | Y | Y |
| Interactive tools | N | N | N | Y |
| Templates/Resources | Y | N | Y | N |
For your company and each competitor, define (or reverse-engineer) their positioning statement:
For [target audience], [product/company] is the [category] that [key benefit/differentiator] because [reason to believe].
Example:
For mid-market SaaS marketing teams, Acme is the campaign management platform that unifies planning and execution in one workspace because it is built on a single data model that eliminates tool fragmentation.
Plot competitors on a 2x2 matrix using the two most important dimensions for your market:
Common axis pairs:
Identify which quadrant is underserved or where your differentiation is strongest.
A competitive battlecard is a one-page reference for sales and marketing teams. Include:
| If the prospect says... | Respond with... |
|---|---|
| "[Competitor] does X too" | "Here is how our approach differs..." |
| "[Competitor] is cheaper" | "Here is what that price difference gets you..." |
| "I've heard good things about [Competitor]" | "They are strong at X. Where we differ is..." |
Questions to ask prospects early that highlight your advantages:
Questions competitors might encourage prospects to ask you, with prepared responses.
Present the full competitive brief with clear formatting. Note the date of the research so the user knows the freshness of the data.
After the brief, ask:
"Would you like me to:
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
pproenca/dot-skills
mattpocock/skills
Useful defaults in competitive-brief — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend competitive-brief for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
competitive-brief reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: competitive-brief is focused, and the summary matches what you get after install.
Registry listing for competitive-brief matched our evaluation — installs cleanly and behaves as described in the markdown.
We added competitive-brief from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for competitive-brief matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: competitive-brief is the kind of skill you can hand to a new teammate without a long onboarding doc.
competitive-brief has been reliable in day-to-day use. Documentation quality is above average for community skills.
competitive-brief reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 57