Best use case
Battlecard is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
## Command
Teams using Battlecard should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/battlecard/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/operations/sales-engine/skills/battlecard/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/battlecard/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Battlecard Compares
| Feature / Agent | Battlecard | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
## Command
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Battlecard ## Command /battlecard <competitor_name> [--refresh] ## Purpose Generate or update a competitive battlecard with positioning, strengths/weaknesses, pricing intelligence, landmine questions, and objection responses. ## Arguments | Arg | Type | Required | Description | |-----|------|----------|-------------| | competitor_name | string | Yes | Competitor to analyze | | --refresh | flag | No | Force refresh even if battlecard exists and is recent | ## Output Genre: battlecard Format: Markdown (Competitive Battlecard template) Produces: 1. **Competitive Profile** -- positioning, reality, market presence 2. **Strengths/Weaknesses** -- verified with sources and ratings 3. **Pricing Intelligence** -- model, range, source, confidence 4. **Win/Loss Scenarios** -- when they win vs when we win 5. **Landmine Questions** -- questions to plant in discovery that expose their weaknesses 6. **Objection Responses** -- what to say when prospect brings them up ## Agent Activation 1. **researcher** (wave 1): Competitive intelligence gathering and verification 2. **copywriter** (wave 2): Objection response copy and positioning language ## Process ``` 1. Check if existing battlecard exists and is < 30 days old (skip research if current) 2. If --refresh or stale: researcher gathers fresh competitive intel 3. Verify all claims against independent sources 4. Rate every data point with source reliability (A-E) 5. Copywriter crafts objection responses and landmine question phrasing 6. Output complete battlecard per researcher's template ``` ## Examples ``` /battlecard "Competitor X" /battlecard "Competitor X" --refresh ```
Related Skills
/do
170
from Miosa-osa/canopy
> The agent's primary skill. Customize this to match your agent's purpose.
/report
170
from Miosa-osa/canopy
> Generate structured reports. Director-owned.
/primary
170
from Miosa-osa/canopy
> Main workflow execution and routing. Director-owned.
Qualify
170
from Miosa-osa/canopy
## Command
Prospect
170
from Miosa-osa/canopy
## Command
Close Plan
170
from Miosa-osa/canopy
## Command
Spec
170
from Miosa-osa/canopy
## Command
Schedule
170
from Miosa-osa/canopy
## Command
Repurpose
170
from Miosa-osa/canopy
## Command
Ideate
170
from Miosa-osa/canopy
## Command
Analyze
170
from Miosa-osa/canopy
## Command
/setup
170
from Miosa-osa/canopy
Full system setup and configuration for OptimalOS.