Agent skill

Battlecards

by growthack88 in growthack88/growth-marketing-os

Creates competitive battlecards for sales deal conversations.

MITAuto-check passedSales & Support

Install Battlecards

skills CLI
$ npx skills add growthack88/growth-marketing-os --skill battlecards -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install growthack88/growth-marketing-os battlecards --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/growthack88/growth-marketing-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/community/battlecards .claude/skills/battlecards && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
battlecards
GitHub stars
116
Token cost
~2.4k tokens
SKILL.md length
825 words
Files
5 (incl. references)
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Creates competitive battlecards for sales deal conversations.

  • Works in 10 steps: Quick facts — Founded, funding,… → When we win — 3 specific scenarios +… → When we lose — 2+ honest losing… → …
  • Tasks that involve Competitor analysis
  • SKILL.md covers Claude Code triggers, Input requirements, Process at a glance and Battlecard structure…, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Battlecards is an agent skill from growthack88/growth-marketing-os. Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per competitor. Outputs a structured markdown battlecard with quick-reference sections for live sales calls. Depends on competitor-research for competitive intelligence and consumes product-messaging, win-loss-analysis, and positioning for framing. Feeds into sales-deck, outreach-emails, and demo-script. Triggered by "battlecard", "competitive intel", "win against…

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/auto-update.md`, `references/battlecard-template.md` and `references/process.md`).

It sits in Sales & Support, covering Competitor analysis and Sales enablement. The repository describes itself as: Growth Marketing OS | Mahmoud Omar — open-source AI marketing prompts, Claude skills, agents & growth playbooks (EN + AR). The licence is MIT.

When your agent uses it

  • Tasks that involve Competitor analysis
  • Tasks that involve Sales enablement

Example prompts

  • “battlecard”
  • “competitive intel”
  • “win against [competitor]”
  • “/battlecards”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Quick facts — Founded, funding, employees, target market, pricing model, starting price (side-by-side table)
  2. When we win — 3 specific scenarios + verbatim customer proof point
  3. When we lose — 2+ honest losing scenarios + mitigation actions
  4. Their pitch — Verbatim competitor language + key claims
  5. Counter-positioning — Scripted "when they say X, we say Y" responses
  6. Feature comparison — Honest table with winner-per-row
  7. Landmines to plant — 3+ discovery questions that expose competitor weaknesses
  8. Objection handling — Common objections with proof-pointed responses
  9. Red flags — When to walk away (qualification-out criteria)
  10. Sources — Every claim with URL + access date + confidence

What it can do on your machine

Read from SKILL.md and the folder at commit c6b55c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Battlecards loads about 2.4k tokens when it runs, and up to ~8.1k if it reads all its reference files. Until then it costs about 145 tokens; SKILL.md has 825 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~145
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from growthack88/growth-marketing-os at commit c6b55c7, republished under its MIT licence (© growthack88). 825 words, ~2,402 tokens.

Download SKILL.mdSave it as .claude/skills/battlecards/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
battlecards
description
Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per competitor. Outputs a structured markdown battlecard with quick-reference sections for live sales calls. Depends on competitor-research for competitive intelligence and consumes product-messaging, win-loss-analysis, and positioning for framing. Feeds into sales-deck, outreach-emails, and demo-script. Triggered by "battlecard", "competitive intel", "win against [competitor]", or "how do we beat [competitor]".
version
1.0
last_updated
2026-02-06
author
marketing-team
goal
Creates competitive battlecards for sales deal conversations.
outcome
Creates competitive battlecards for sales deal conversations. Produces win themes, landmines to plant, objection handlers, and competitive positioning per…
primitive
sales-enablement
ontology_type
battlecard
review_gate
2
inputs.recommended
competitor-research, product-messaging, win-loss-analysis, positioning
feeds_into
demo-script, outreach-emails, sales-deck
<!--
COMMUNITY SKILL — included under its original MIT license.
Source: https://github.com/matteotitta/genesys-skills by Matteo Titta (MIT).
License text: ../LICENSE-genesys-skills.txt
Curated into Growth Marketing OS by Mahmoud Omar (mahmoudomar.com) — this file
is NOT original work by the repo author; see /skills/community/README.md.
-->

Battlecards

Quick-reference competitive intelligence battlecards for live sales conversations. Designed to be scanned in 30 seconds during a call. Supports batch generation for multiple competitors with confidence-level sourcing on every claim.

The body of this file holds decision-grade context (when to invoke, inputs, structure, anti-hallucination guardrails, gotchas). Step-by-step process, output template, quality gates, and feedback loops live in references/.


Claude Code triggers

Invoke this skill when user says:

  • "Create battlecard for [competitor]"
  • "Competitive battlecard"
  • "How to win against [competitor]"
  • "Competitive intel for sales"
  • "Battlecards for [product]"
  • "Sales battlecard"
  • "Counter-positioning against [competitor]"
  • "Competitive one-pager" (if focus is on win/lose scenarios)

Do NOT invoke when:

  • User wants deep competitor research → Use /competitor-research skill
  • User wants sales deck → Use /sales-deck skill
  • User wants demo script → Use /demo-script skill
  • User wants competitive feature comparison only → Use /competitor-research skill

Input requirements

Required inputs
InputDescriptionSource
Competitor name(s)Which competitor(s) to create battlecards forUser specifies
Your product contextWhat you sell, key capabilitiesUser, product-messaging, or URL
Optional inputs (improve quality)
InputHow it helps
competitor-research outputPre-researched intel (funding, features, positioning)
win-loss-analysis outputWhen we win/lose patterns with evidence
Product messagingCounter-positioning based on your value props
Positioning contextStrategic anchors for competitive framing
Competitor URLsFor live research if no prior research exists
Sales call transcriptsReal objections and competitive mentions
Input validation checklist

Before proceeding, verify:

  • Competitor(s) confirmed
  • Your product's key differentiators known
  • At least one intel source available (research, URL, or docs)

If inputs are missing: Ask which competitor(s). Offer to run competitor-research first if no intel available.


Process at a glance

PhasePurposeOutput
1. Competitor selectionConfirm scope (single vs batch)Confirmed competitor list
2. Intel gatheringPull from research + win-loss + web researchIntel dossier per competitor
3. Battlecard generationFill template, add confidence levels, write talk tracks + landminesDraft battlecard(s)
4. Validation & deliveryVerify sources, format for deliveryFinal battlecard(s)

Full step-by-step (with checkpoints, confidence framework, workflow sequences, GDrive export commands) in references/process.md.


Battlecard structure (decision-grade)

Every battlecard contains these sections — in this order, no exceptions:

  1. Quick facts — Founded, funding, employees, target market, pricing model, starting price (side-by-side table)
  2. When we win — 3 specific scenarios + verbatim customer proof point
  3. When we lose — 2+ honest losing scenarios + mitigation actions
  4. Their pitch — Verbatim competitor language + key claims
  5. Counter-positioning — Scripted "when they say X, we say Y" responses
  6. Feature comparison — Honest table with winner-per-row
  7. Landmines to plant — 3+ discovery questions that expose competitor weaknesses
  8. Objection handling — Common objections with proof-pointed responses
  9. Red flags — When to walk away (qualification-out criteria)
  10. Sources — Every claim with URL + access date + confidence

Full template with field-level guidance in references/battlecard-template.md. Output wrapper format and iteration prompts in references/auto-update.md.


Show full SKILL.md (373 more words)Show less

Anti-hallucination guardrails

Critical for sales credibility:

  1. Never invent competitor claims. Only use verified data with sources.
  2. Never fabricate customer quotes. Verbatim only or mark "[PLACEHOLDER: need customer quote]".
  3. Never guess competitor pricing. Use verified data or mark "[CONFIRM: pricing]".
  4. Mark confidence levels on all competitive intel (High/Medium/Low/UNVERIFIED).
  5. Cite sources for all factual claims with access dates.
  6. Acknowledge gaps rather than fill with plausible content.
  7. Be honest about weaknesses. "When we lose" builds credibility with sales team.

Gotchas

  • Fabricated competitor pricing: Invents pricing tiers when pricing page is gated or not found → Mark pricing as [UNAVAILABLE] and note where to find it (sales call, demo request). Never guess.
  • Generic objection handlers: Produces "we're more reliable" instead of specific counter-arguments → Every objection handler must reference a concrete differentiator or proof point.
  • Missing landmines: Only covers strengths, forgets to include questions that expose competitor weaknesses → Landmines are the most valuable section for sales reps. 3-5 questions per competitor minimum.
  • Stale competitive data: Uses old competitor positioning without checking current website → Always scrape competitor website at time of battlecard creation. Note access date.

Integration with other skills

Upstream skills (provide inputs)
SkillWhat it providesRequired?
competitor-researchCompany facts, positioning, features, pricingRecommended
win-loss-analysisWin/loss patterns, objections, proof pointsRecommended
product-messagingYour value props for counter-positioningRecommended
positioningStrategic competitive anchorsOptional
Downstream skills (consume outputs)
SkillHow it uses battlecards
sales-deckDifferentiation slide content
demo-scriptObjection handling during demos
outreach-emailsCompetitive displacement email content

Reference files

FilePurpose
references/process.md4-phase runbook + flowchart + confidence framework + workflow sequences
references/battlecard-template.mdComplete battlecard structure with field-level examples
references/quality.mdPre-delivery checklist + self-evaluation protocol + anti-examples
references/auto-update.mdOutput wrapper, iteration prompts, feedback signal detection, pattern rules

MCP data integration

Level: 2 — PM Execution (inherits upstream, no unique pulls)

Inherits from: competitor-research, win-loss-analysis, product-messaging

Pulls fresh: NONE — all data comes from upstream. Battlecards synthesize existing competitor research and win-loss patterns.

Fallback (no MCP): Use competitor-research and win-loss-analysis outputs directly. If upstream skills haven't run, trigger them first before running battlecards.


Changelog

VersionDateChanges
1.02026-02-06Initial skill creation. Extracted from sales-enablement with dedicated process, confidence framework, batch support, and Google Docs/PDF export
1.12026-05-01Slim refactor: extracted process, quality, and auto-update protocol to references/ (Phase 4.5.1.C)

© growthack88, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/community/battlecards of growthack88/growth-marketing-os.

  • SKILL.md
  • references/auto-update.md
  • references/battlecard-template.md
  • references/process.md
  • references/quality.md

Open the folder on GitHubat commit c6b55c7

Compare with similar skills

Battlecards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Battlecards compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Battlecards this skillgrowthack88/growth-marketing-os116—~2.4kAutomated safety check: PassMIT
Sales Enablement Kitaaron-he-zhu/aaron-marketing-skills2.9k—~3.3kAutomated safety check: PassApache-2.0
Competitive Battlecardphuryn/pm-skills27k—~721Automated safety check: PassMIT
Battlecard Generatorgooseworks-ai/goose-skills1.2k1 repos~2.3kAutomated safety check: PassMIT
Gtm Competitive Battlecard Writercriptogus/agent-evolve-network288—~551Automated safety check: PassCC-BY-SA-4.0
Competitive Intelligencew95/awesome-claude-corporate-skills244—~3.1kAutomated safety check: PassMIT

Similar skills

  • Sales Enablement Kit

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch…

    2.9k GitHub stars~3.3k tokensUpdated today
    Sales & SupportAuto-check passed
  • Competitive Battlecard

    phuryn/pm-skills

    Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns.

    27k GitHub stars~721 tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Battlecard Generator

    gooseworks-ai/goose-skills

    Research a specific competitor across their website, reviews, ads, social presence, and pricing — then produce a structured sales battlecard with positioning traps, objection handlers, landmine…

    1.2k GitHub starsUsed in 1 repo~2.3k tokens
    Sales & SupportAuto-check passed
  • Gtm Competitive Battlecard Writer

    criptogus/agent-evolve-network

    Writes seller-ready battlecards: positioning, traps, landmines, objection handling, and proof points.

    288 GitHub stars~551 tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • Competitive Intelligence

    w95/awesome-claude-corporate-skills

    Research your competitors and build an interactive battlecard.

    244 GitHub stars~3.1k tokensUpdated 7 mo ago
    Sales & SupportAuto-check passed
  • Afrexai Competitive Intel

    LeoYeAI/openclaw-master-skills

    Complete competitive intelligence system — market mapping, product teardowns, pricing intel, win/loss analysis, battlecards, and strategic monitoring.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Sales & SupportAuto-check passed

More from growthack88/growth-marketing-os

All 13 skills in this repo
  • Mena Ads

    growthack88/growth-marketing-os

    MENA Ads Command Center — a complete paid-ads operating system for the Arab world (Egypt, KSA, UAE, GCC, Levant, North Africa) and global accounts.

    116 GitHub stars~2.5k tokensUpdated 8 days ago
    Auto-check passed
  • Arabic Copy Localizer

    growthack88/growth-marketing-os

    Marketing copy localization skill that converts English marketing copy (ads, landing pages, emails, CTAs) into native Egyptian Arabic عامية — or GCC dialect on request — with natural English…

    116 GitHub stars~1k tokensUpdated 8 days ago
    Auto-check passed
  • Benchmark Analyst

    growthack88/growth-marketing-os

    Marketing benchmark triage skill. An agent skill from growthack88/growth-marketing-os.

    116 GitHub stars~1.2k tokensUpdated 8 days ago
    Auto-check passed
  • Cod Operations Analyst

    growthack88/growth-marketing-os

    COD (cash-on-delivery) e-commerce operations skill. An agent skill from growthack88/growth-marketing-os.

    116 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed
  • Conversion Copywriter

    growthack88/growth-marketing-os

    Direct-response copywriting skill. An agent skill from growthack88/growth-marketing-os.

    116 GitHub stars~1.4k tokensUpdated 8 days ago
    Auto-check passed
  • Funnel Decomposition Analyst

    growthack88/growth-marketing-os

    Senior performance analyst skill that answers "why did sales drop (or jump)?" using rigorous funnel decomposition.

    116 GitHub stars~861 tokensUpdated 8 days ago
    Auto-check passed

Questions about Battlecards

What does Battlecards do?

Creates competitive battlecards for sales deal conversations. Battlecards is an agent skill from growthack88/growth-marketing-os. Creates competitive battlecards for sales deal conversations.

When should I use Battlecards?

Battlecards fits situations like: tasks that involve Competitor analysis; tasks that involve Sales enablement.

How do I install Battlecards in Claude Code?

Run `npx skills add growthack88/growth-marketing-os --skill battlecards -a claude-code`. Or copy the skill folder (skills/community/battlecards in growthack88/growth-marketing-os) into .claude/skills/battlecards in your project. Claude Code loads it when a task matches its description.

How do I install Battlecards in Codex?

Run `npx skills add growthack88/growth-marketing-os --skill battlecards -a codex`. Or copy the skill folder (skills/community/battlecards in growthack88/growth-marketing-os) into .agents/skills/battlecards in your project. Codex loads it when a task matches its description.

Can I use Battlecards in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthack88/growth-marketing-os --skill battlecards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/battlecards, .gemini/skills/battlecards, .github/skills/battlecards and .opencode/skills/battlecards in your project.

What does Battlecards need to run?

SKILL.md names no scripts, command-line tools or credentials: Battlecards is instructions for the agent only.

Does Battlecards access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Battlecards safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Battlecards use?

Battlecards is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Battlecards use?

About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.7k tokens, read only when the agent opens those files.

What are the alternatives to Battlecards?

Skills that share tags, products or a category with Battlecards: Sales Enablement Kit (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Competitive Battlecard (phuryn/pm-skills, 27k stars), Battlecard Generator (gooseworks-ai/goose-skills, 1.2k stars) and Gtm Competitive Battlecard Writer (criptogus/agent-evolve-network, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Battlecards?

growthack88 (a GitHub user) maintains it in growthack88/growth-marketing-os, which has 116 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 2, 2026.

Source: growthack88/growth-marketing-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.