Agent skill
battlecard-system
Use to standardize competitive positioning, objection handling, and talk tracks across teams.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/battlecard-system
SKILL.md
Battlecard System Skill
When to Use
- Launching new competitive programs or product updates.
- Training teams ahead of major deals or campaigns.
- Refreshing differentiators based on win/loss analysis.
Framework
- Competitive Intel – capture strengths, weaknesses, proof, and trigger signals per competitor.
- Messaging Pillars – align headline, supporting proof, and objection responses.
- Delivery Format – deck, one-pager, LMS module, and short-form scripts.
- Distribution & Access – tag assets, set expiration dates, and embed in enablement tools.
- Feedback Loop – collect field feedback, update win/loss data, and refresh quarterly.
Templates
- Battlecard layout (overview, talk track, objections, proof points).
- Objection handling matrix.
- Competitive win/loss capture form.
Tips
- Keep “permission to win” statements crisp; avoid feature dumping.
- Include audio/video snippets from top performers.
- Align with legal/product teams before publishing sensitive data.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?