gtm-engineer-playbook: Skill for Claude Code

.claude/skills/gtm-playbook/competitive-battlecard-generator/SKILL.md

competitive-battlecard-generator is a skill for Claude Code from Othmane-Khadri/gtm-engineer-playbook. It costs 78 tokens per session (4,040 once invoked), scanned A, original, MIT.

A research-based guide for creating competitive battlecards: concise documents that help sales teams compare a product with competing products. It gathers information about competitor strengths, weaknesses, positioning, objections, and useful questions.

In plain words
What is it for?
Use it to analyze one to five competitors, prepare competitive positioning, handle objections, and create questions for sales conversations. It requires company and competitor context before producing a battlecard.
Why use it?
It helps sales teams prepare for deals where customers are comparing alternatives. Research-backed comparisons make it easier to respond to objections and explain differences.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Othmane-Khadri/gtm-engineer-playbook's own configuration. It tells Claude Code how to work on gtm-engineer-playbook itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gtm-engineer-playbook configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Othmane-Khadri/gtm-engineer-playbook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Othmane-Khadri/gtm-engineer-playbook/main/.claude/skills/gtm-playbook/competitive-battlecard-generator/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Othmane-Khadri/gtm-engineer-playbook

Made for: Claude Code.

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-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/othmane-khadri/gtm-engineer-playbook/competitive-battlecard-generator/github.svg)](https://agentmods.dev/skills/othmane-khadri/gtm-engineer-playbook/competitive-battlecard-generator)
Your own site
<a href="https://agentmods.dev/skills/othmane-khadri/gtm-engineer-playbook/competitive-battlecard-generator"><img src="https://agentmods.dev/badge/skills/othmane-khadri/gtm-engineer-playbook/competitive-battlecard-generator/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-generator

Your own site · 80×15
<a href="https://agentmods.dev/skills/othmane-khadri/gtm-engineer-playbook/competitive-battlecard-generator"><img src="https://agentmods.dev/badge/skills/othmane-khadri/gtm-engineer-playbook/competitive-battlecard-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,040 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.00078 $0.04040
Opus 5 $0.00039 $0.02020
Sonnet 5 $0.00016 $0.00808
Haiku 4.5 $0.00008 $0.00404

Measured 12d ago against content hash 66000fbfe942, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

competitive-battlecard-generator 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 12d ago.

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.

.claude/skills/gtm-playbook/competitive-battlecard-generator/SKILL.md · 401 lines

How it starts

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

Competitive Battlecard Generator

Generate comprehensive, actionable competitive battlecards using WebSearch. Each battlecard gives sales teams the intelligence they need to win competitive deals — competitor strengths, weaknesses, objection handling, and trap questions, all grounded in real research. Can batch-process up to 5 competitors in a single run.


Activation

When the user triggers this skill, follow the steps below in order. Do NOT skip the input step. Do NOT produce a battlecard without gathering context first.


Step 1 — Collect Input

Ask the user for these inputs all at once in a numbered list:

I need some context before building your battlecard(s). Answer these questions:

1. What is your company name and what do you do? (one sentence)
2. Which competitor(s) do you want a battlecard for? (1-5 names)
3. (Optional) What are your key differentiators? (3-5 bullets)
4. (Optional) Any known weaknesses of the competitor(s)?
5. (Optional) Are you usually compared to them? In what context?

Rules for this step:

  • Wait for the user to respond before proceeding. Do NOT generate placeholder answers.
  • Only question 1 and 2 are required. If either is missing, ask again.
  • If the user provides more than 5 competitors, tell them you will batch the first 5 and they can run the skill again for the rest.
  • If the user provides optional inputs, use them to sharpen the analysis. If they skip optionals, proceed without them — you will research independently.

Step 2 — Competitor Overview

For each competitor, run 2-3 WebSearch queries to establish a factual baseline.

Search patterns:

  • "{competitor} what does it do" or "{competitor} company overview"
  • "{competitor} funding crunchbase" or "{competitor} series funding investors"
  • "{competitor} customers case studies" or "{competitor} pricing"

Gather these data points:

Field Description
What they do Their positioning statement — how they describe themselves (from their homepage or about page)
Founded Year founded
HQ Headquarters location
Company size Employee count range
Funding Total raised, last round, key investors (for private companies)
Key customers Named logos from case studies, website, or press releases (3-8 names)
Target market Who they sell to — company size, industry, buyer persona
Pricing model Pricing tiers, per-seat, usage-based, etc. If not publicly available, write "Pricing not publicly available — ask during discovery"
Recent news 1-3 headlines from the last 90 days with source URLs

Read the full file on GitHub · 401 lines

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. 12d ago First seen · 401 lines · 78 tokens per session scan A 66000fbfe942

Subscribe to this mod's changes

competitive-battlecard-generator is a skill published in the GitHub repository Othmane-Khadri/gtm-engineer-playbook (56 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 4,040 once invoked, about $0.0004 per session on Opus 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-08-30.

Related

Other skills, from other repositories

go-to-market-playbook

A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.

Gingiris-1031/gingiris-skills · 48 tokens

adoption-leaderboard

Scores a rep's or a team's recent sales calls against a fixed set of five winning-behavior checklists (rapport, upsell signals, renewal risk, customer experience, value realization), then ranks reps lowest-adoption-first so the highest-leverage coaching targets lead. Use when running a team calibration, prepping 1:1…

zime-ai/zime-gtm-skills · 96 tokens

challenger

Audits a B2B sales call transcript against the Challenger Sale framework (teach, tailor, take control, plus the commercial-teaching pitch arc), or sweeps a CRM export for deals with no teaching insight logged. Use when a rep leans on discovery-question skill but rarely brings a point of view, when prepping a rep for a…

zime-ai/zime-gtm-skills · 104 tokens

champion-tracker

Tracks champion strength across a deal's call(s) — builds an action ledger, one row per named contact per cited quote, tagging each as either an act of internal selling (looping in a stakeholder, pushing back for the rep in a room the rep wasn't in) or mere positive sentiment (encouraging words, no action), then reads…

zime-ai/zime-gtm-skills · 112 tokens

end-client-registration

Audits a partner/reseller's end-client deal registration for completeness — partner identity, end-client entity kept distinct from the partner, engagement scope, conflict check against the direct pipeline, confirmed permission to engage the end-client contact, commercial terms, and an expiry window. Use when reviewing…

zime-ai/zime-gtm-skills · 108 tokens

executive-briefing

Writes the short brief a rep sends upward out of one deal — to their own exec or the buyer's exec sponsor — covering deal snapshot, status, what's at risk, and the ask, each claim cited to a quote or a CSV column/cell. Use when someone who will never read the transcript needs to act on one deal, not a call-by-call…

zime-ai/zime-gtm-skills · 86 tokens