Create a concise, sales-ready battlecard for use against a specific competitor.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncompetitive-battlecardExecute the skills CLI command in your project's root directory to begin installation:
Fetches competitive-battlecard from phuryn/pm-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-battlecard. Access via /competitive-battlecard 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
9.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
9.6K
stars
Create a concise, sales-ready battlecard for use against a specific competitor.
You are creating a competitive battlecard for $ARGUMENTS.
Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.
Research the competitor (use web search):
Create the battlecard with these sections:
| Capability | Us | Them | Winner |
|---|---|---|---|
| [Feature area 1] | [Our approach] | [Their approach] | [Us/Them/Tie] |
| [Feature area 2] | ... | ... | ... |
| Pricing | ... | ... | ... |
| Support | ... | ... | ... |
| Prospect Says | Respond With |
|---|---|
| "Competitor X has [feature]" | "[Our alternative approach and why it's better for them]" |
| "They're cheaper" | "[Value framing: total cost of ownership, ROI, hidden costs]" |
| "They're more established" | "[Our advantages: speed, innovation, focus, support]" |
Questions to ask the prospect that highlight competitor weaknesses:
Keep it scannable: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.
Save as markdown. Format for easy printing or sharing in Notion/Confluence.
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
Useful defaults in competitive-battlecard — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend competitive-battlecard for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
competitive-battlecard has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: competitive-battlecard is focused, and the summary matches what you get after install.
I recommend competitive-battlecard for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in competitive-battlecard — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: competitive-battlecard is the kind of skill you can hand to a new teammate without a long onboarding doc.
competitive-battlecard is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added competitive-battlecard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
competitive-battlecard reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 55