competitive-battlecard

competitive-battlecard is a skill for Claude Code from stefanoskarakasis/Product-Marketing-Skills. It costs 124 tokens per session (5,961 once invoked), scanned A, original, MIT.

A skill that creates a one-page competitor battlecard for one sales deal. It adapts the card to the seller's role, sales approach, buyer, deal stage, and the competitor's position.

In plain words
What is it for?
Use it to decide what to say first, what to ask, how to answer buyer objections, when to continue pursuing the deal, and when to stop.
Why use it?
It turns competitive research and approved evidence into advice a seller can skim before a call and quote during it. It also separates deal-specific guidance from broader market or product documents.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions .claude-plugin.

Part of the pmm-competitive-intelligence plugin — 2 skills, 5 commands, 8 MCP servers shipped together

Good fit Use it to decide what to say first, what to ask, how to answer buyer objections, when to continue pursuing the deal, and when to stop.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stefanoskarakasis/product-marketing-skills/competitive-battlecard
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add stefanoskarakasis/Product-Marketing-Skills --skill competitive-battlecard
Clone the repo
git clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-Skills

Made for: Claude Code.

Or install pmm-competitive-intelligence, the plugin that ships this one along with the rest of its 2 skills, 5 commands, 8 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for competitive-battlecard

README.md
[![agentmods](https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/competitive-battlecard/github.svg)](https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/competitive-battlecard)
Your own site
<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/competitive-battlecard"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/competitive-battlecard/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for competitive-battlecard

Your own site · 80×15
<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/competitive-battlecard"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/competitive-battlecard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,961 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00124 $0.05961
Opus 5.5 $0.00050 $0.02384
Sonnet 5.5 $0.00025 $0.01192
Haiku 4.5 $0.00012 $0.00596

Measured yesterday against content hash 6c9624984fe6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

competitive-battlecard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

pmm-competitive-intelligence/skills/competitive-battlecard/SKILL.md · 248 lines

How it starts

The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Competitive Battlecard

A battlecard is read once, five minutes before a call, and quoted from memory in the call. This skill builds that one page for one competitor in one deal: what to say first, what to ask, what to say when the buyer pushes back, when to lean in and when to walk away. It does not research the market or map alternatives; it takes the alternatives map and the proof registry already in your brain, adds fresh evidence about the named competitor, tailors the result to who is selling to whom at what stage, and proposes what it learned back into brain Section 3 for you to confirm.

Trigger

  • When: A seller or PMM needs a competitor-specific play for a live or upcoming deal, or a refresh of an existing card.
  • Not for: Mapping who buyers compare you to → alternatives-map. A weekly read on what changed → signal-monitor. Registering or checking a claim → proof-points. A feature-level handoff doc with one comparison → product-messaging-playbook. Persona cards and a competitive playbook as part of a positioning build → positioning-messaging (SALES-ENABLEMENT mode). A multi-skill competitive program → workflow-orchestrator.
  • Example prompts:
    • "Battlecard for [competitor]"
    • "How do we beat [competitor] with a CFO in the evaluation stage?"
    • "[Competitor] is in my deal, what do I say?"
    • "They say [claim]. How do I counter it?" (edge: one objection, answered from the card's blocks)
    • "Refresh the [competitor] card" (edge: compares with the last saved card)

Inputs

  • Args: The competitor (required; doing nothing or a spreadsheet counts). Optional: role, GTM motion, the competitor's status in the deal, buyer persona, deal stage, segment and region, what the buyer actually said, delivery format (Google Doc or HTML). Missing items are asked once in Step 2.
  • Defaults: Role account executive, buyer general, stage evaluation, competitor a challenger alongside us, delivery Google Doc. A skipped answer is stated as an assumption on the card.
  • Context keys:
    • /foundation/brain.md (optional, sharper with it): Sections 1 to 8, see the contract.
    • /foundation/me.md (optional): format and detail only.
    • /foundation/gaps.md (append only).
    • /context/battlecards/ (earlier cards for this competitor), /context/signals/ (recent signal-monitor runs), /context/meta-patterns.md (guardrails).
    • ~~CRM, ~~call recordings, ~~competitive intelligence, ~~win/loss, ~~team chat, ~~reviews, ~~market data, ~~company data, ~~knowledge base, ~~cloud storage, or pasted material.
    • Brain contract: Reads: Section 1 (permitted claims, offerings, glossary), 2 (persona, economic buyer, champion, pains, triggers, anti-persona), 3 (alternatives, status quo, why they leave, unique capabilities, alt_shortfalls, switching_forces, objections with approved responses, and the Alternatives Map block for this competitor), 4 (language preferences, forbidden phrases, customer_phrases), 5 (why now), 6 (approved metrics, approved quotes, forbidden claims), 7 (priorities), 8 (prohibited, approvals, stakeholders). Writes: Section 3 only, as one appended Battlecard Field Notes block or a one-line stub, after you confirm the exact text. Never writes to: Sections 1, 2, 4, 5, 6, 7, 8.

Read the full file on GitHub · 248 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday Changed 6c9624984fe6
  2. 2d ago Changed · +1 lines 81dc7dc367e4
  3. 3d ago First seen · 247 lines · 124 tokens per session scan A 50f93f3ee1f5

Subscribe to this mod's changes

competitive-battlecard is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (7 stars, last pushed yesterday), licensed MIT. It adds 124 tokens to every session and 5,961 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-13.

Related

Other skills, from other repositories

becoming-senior-pm

Use this skill when the user asks "how do I become a senior PM", "what does senior PM actually mean", "I want to get promoted to senior", "what's the difference between PM and senior PM", "I've been a PM for 2–3 years and want to grow", "my manager says I need to work more strategically", "I'm stuck at PM level", or…

Productfculty-aipm/PM-Copilot-by-Product-Faculty · 126 tokens

founding-pm

Use this skill when the user says "I'm the first PM", "founding PM", "I joined a startup as the only PM", "how do I set up PM processes from scratch", "no PM infrastructure exists", "I'm building the PM function", "what should a first PM do in 90 days", or is navigating the unique challenges of being an early-stage PM…

Productfculty-aipm/PM-Copilot-by-Product-Faculty · 106 tokens

eval-suite-design

Use this skill when the user asks to "design an eval suite", "build evals for my AI feature", "create an evaluation framework", "how do I evaluate my AI", "what evals should I run", "build an eval system", or wants to create a systematic evaluation framework for an AI-powered product feature. Typically run after…

Productfculty-aipm/PM-Copilot-by-Product-Faculty · 83 tokens

improvement-flywheel

Use this skill when the user asks about "continuous improvement for AI", "AI quality flywheel", "how do we keep improving our AI feature", "closing the eval feedback loop", "systematic AI improvement process", or wants to build a repeating process that continuously improves AI product quality over time rather than…

Productfculty-aipm/PM-Copilot-by-Product-Faculty · 72 tokens

llm-as-judge

Use this skill when the user asks to "set up LLM as a judge", "write an LLM judge prompt", "automate quality evaluation", "use Claude to evaluate outputs", "build an automated eval", "LLM-based evaluation", or wants to create a scalable automated evaluation system where one LLM grades the outputs of another LLM.

Productfculty-aipm/PM-Copilot-by-Product-Faculty · 77 tokens

memory

Use this skill when the user asks to "update my PM Copilot memory", "save this to my profile", "remember that", "update my context", "update my product context", "save this decision", "add this to my memory", "track this risk", "mark this risk as resolved", "add a lesson learned", "save these stakeholder notes", or…

Productfculty-aipm/PM-Copilot-by-Product-Faculty · 150 tokens