dotfiles/dot_config/skillshare/skills/competitive-battlecard/SKILL.md
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'
npx skillsauth add pkking/dotfiles competitive-battlecardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
databases
Generate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each step, and writing .env files and GitHub Actions secrets.
testing
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
development
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
development
Grill me about specs for the workflows I want to build, within this workspace.