How to use the Competitive Battlecard agent skill

What the competitive-battlecard skill makes the agent do

When you name a competitor, the agent uses web search to look up that company's current product, pricing, positioning, and recent changes. It also checks known strengths and weaknesses and customer sentiment on sites such as G2, Capterra, and Reddit.

The result is a one-page reference sheet for sales reps, saved as markdown so it can be printed or pasted into Notion or Confluence. The sheet includes a quick comparison table, where you win and where they win, ready-made answers to common objections, questions to ask prospects, and win/loss patterns.

• Company overview: founding details, HQ, funding or revenue if public, target market, and a one-sentence positioning
• Quick comparison table with a winner for each capability, including pricing and support
• Where we win and where they win, with proof points or counter-positioning
• Common objections and responses, such as 'They're cheaper' or 'They're more established'
• Landmines to plant: questions that surface competitor weaknesses
• Win/loss patterns and the key differentiator in competitive deals

Install the competitive-battlecard skill

Download the ZIP for this skill from our page. The skill is a folder containing a single file, SKILL.md. Unzip it so that the competitive-battlecard folder sits inside one of the following locations:

For a personal skill available in all your projects, unzip it into ~/.claude/skills/. For a skill that only applies to one project, unzip it into that project's .claude/skills/ folder.

In the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/competitive-battlecard/
• Project only: .claude/skills/competitive-battlecard/ inside your project folder
• Claude apps: Settings → Capabilities → Skills

Trigger the skill with natural requests

You do not need a special command. Ask in plain language and include the competitor's name, since the skill is built around one specific competitor. The skill's description covers requests to prepare sales teams, create competitive materials, or respond to 'why not competitor X?'.

If you have your own material, mention it in the same request. The skill reads any feature lists, win/loss data, or sales call notes you provide before doing its own research, so the output reflects your real data.

• 'Create a battlecard for [competitor name].'
• 'Prepare our sales team for deals against [competitor name].'
• 'A prospect asked why not [competitor name]. Help me answer.'
• 'Using my feature list and call notes, build a battlecard against [competitor name].'

What the skill needs to run

The skill depends on live research, so the host agent must have web search capability. Without it, the instructions cannot gather current competitor information.

Your own files are optional. Feature lists, win/loss data, and sales call notes are helpful inputs but are not required. According to the listing, the skill runs no scripts and uses the network.

• Web search capability in the host agent (required)
• Optional: your feature lists, win/loss data, or sales call notes as input files

Safety notes before sales uses the output

Web research can be outdated or wrong. Check pricing and every competitor claim against current sources before sales reps use them, and especially before using any claim publicly.

The skill does not verify accuracy or compliance. Do not rely on it for legal or regulatory comparisons, such as advertising claims. Final decisions on pricing or claims need human review.

• Verify pricing and feature claims yourself
• Have legal or compliance review any public comparison
• The listing states the skill runs no scripts and uses network access

Tips for getting a useful battlecard

Give the agent more context. Your own feature lists and win/loss notes let it ground the comparison in your product rather than generic claims.

Ask for one competitor at a time. The format is built around a single company, so separate requests produce cleaner sheets than one request covering several.

Review the 'Winner' column and the objection responses with your product team. These are the parts most likely to need adjustment.

• Upload real call notes so objection responses reflect what prospects actually say
• Re-run the battlecard when a competitor launches something new, since the research is current only at the time it runs
• Print or share the markdown output in Notion or Confluence for reps to reference during calls