Case Study Builder
BrianRWagner/ai-marketing-claude-code-skills
Turns a client win into case studies, proposal blurbs, social proof quotes and sales stories, after collecting the details and at least one concrete number.
Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies.
Install Sales Enablement
$ npx skills add cbrock84/headcount --skill sales-enablement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount sales-enablement --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/revenue/skills/sales-enablement .claude/skills/sales-enablement && rm -rf skills-srcUse ~/.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/
Install the "sales-enablement" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablement into .claude/skills/sales-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill sales-enablement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount sales-enablement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/revenue/skills/sales-enablement .agents/skills/sales-enablement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sales-enablement" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablement into .agents/skills/sales-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill sales-enablement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount sales-enablement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/revenue/skills/sales-enablement .cursor/skills/sales-enablement && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sales-enablement" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablement into .cursor/skills/sales-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/revenue/skills/sales-enablement--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill sales-enablement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount sales-enablement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/revenue/skills/sales-enablement .gemini/skills/sales-enablement && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sales-enablement" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablement into .gemini/skills/sales-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount sales-enablementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill sales-enablement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/revenue/skills/sales-enablement .github/skills/sales-enablement && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sales-enablement" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablement into .github/skills/sales-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill sales-enablement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount sales-enablement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/revenue/skills/sales-enablement .opencode/skills/sales-enablement && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sales-enablement" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/revenue/skills/sales-enablement into .opencode/skills/sales-enablement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sales-enablement- GitHub stars
- 2k
- Token cost
- ~783 tokens
- SKILL.md length
- 439 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies.
- Tasks that involve Sales enablement
- SKILL.md covers Know where deals actually stall, The core set, Demo and Maintaining, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sales Enablement is an agent skill from cbrock84/headcount. Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in Sales & Support, covering Sales enablement. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
When your agent uses it
- Tasks that involve Sales enablement
Example prompts
- “Use the sales-enablement skill to build what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo…”
- “/sales-enablement”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. 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
No URLs in SKILL.md.
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
Sales Enablement loads about 783 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 439 words of instructions outside code blocks.
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 cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 439 words, ~783 tokens.
Download SKILL.mdSave it as
.claude/skills/sales-enablement/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- sales-enablement
- description
- Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.
Sales enablement
Collateral gets used when it solves a problem the seller has in a live conversation. Everything else is filed and forgotten.
Know where deals actually stall
Before making anything, find where deals die: first call, after the demo, at pricing, at security review, at the champion's boss. Each stall has a different remedy, and building for the wrong one produces beautifully designed collateral nobody opens.
The core set
Pitch deck — a structure, not a script. Problem the buyer recognizes, why current approaches fail, what you do differently, proof, commercials, next step. Ten to fifteen slides, each with a takeaway headline.
One-pager — what the champion forwards internally to people you will never meet. It must survive being read with no context and no presenter. This is usually the highest-leverage asset and the most neglected.
Objection handling — the real objections, in the words prospects use, with responses that acknowledge the legitimate part first. A response that denies the objection reads as evasion and ends trust.
Battlecards — per competitor: where they genuinely win, where you do, the traps to avoid, and what to say when the prospect raises them. Cards claiming you win everywhere get ignored by sellers, who know better.
Case studies — situation, what changed, measurable result, in the buyer's language. One verifiable number beats a page of adjectives.
Demo
Demo the outcome, not the interface. Start where the value is visible, not at login and settings.
Tailor to the problem they told you about — a feature tour of everything demonstrates that you were not listening. Prepare for the three things that always go wrong, and know how to reach the value moment inside five minutes when time gets cut.
Show full SKILL.md (159 more words)Show less
Maintaining
Collateral rots. Every asset needs an owner and a review date, and anything referencing pricing, competitors, or product capability needs checking every quarter. A battlecard describing a competitor's old product loses deals.
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Never
- Build collateral before you know where deals actually stall. Ask the reps and read the losses first.
- Ship a deck or one-pager with no owner and no review date. Unmaintained collateral is worse than none.
- Order a demo around the product's feature list instead of the order the buyer's problem unfolds in.
- Count enablement as done at delivery. It is done when reps use it in live deals.
© cbrock84, 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 1 other file (references) in plugins/revenue/skills/sales-enablement of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Sales Enablement 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sales Enablement this skillcbrock84/headcount | 2k | — | ~783 | Automated safety check: Pass | MIT | |
| Case Study BuilderBrianRWagner/ai-marketing-claude-code-skills | 441 | — | ~1.8k | Automated safety check: Pass | None | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sales Enablementcoreyhaines31/marketingskills | 54k | — | ~5.2k | Automated safety check: Pass | MIT | |
| Eol Internal Enablementdeanpeters/Product-Manager-Skills | 7.2k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Objection Handlinggtmagents/gtm-agents | 414 | 1 repos | ~399 | Automated safety check: Pass | Apache-2.0 |
Similar skills
B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
Sales Enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts.
Eol Internal Enablement
deanpeters/Product-Manager-Skills
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.
Objection Handling
gtmagents/gtm-agents
A skill your agent uses when preparing responses to prospect objections during outbound, discovery, or follow-up conversations.
Msp Sales
RTFM-IT-Services-LLC/msp-claude-skills
A skill your agent uses whenever the user wants sales documents, content, or procedures for their managed IT services (MSP) business: cold outreach emails or sequences, call scripts or talk tracks…
More from cbrock84/headcount
All 178 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI ML Governance
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Related
Categories
Questions about Sales Enablement
What does Sales Enablement do?
Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Sales Enablement is an agent skill from cbrock84/headcount. Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies.
When should I use Sales Enablement?
Sales Enablement fits situations like: tasks that involve Sales enablement.
How do I install Sales Enablement in Claude Code?
Run `npx skills add cbrock84/headcount --skill sales-enablement -a claude-code`. Or copy the skill folder (plugins/revenue/skills/sales-enablement in cbrock84/headcount) into .claude/skills/sales-enablement in your project. Claude Code loads it when a task matches its description.
How do I install Sales Enablement in Codex?
Run `npx skills add cbrock84/headcount --skill sales-enablement -a codex`. Or copy the skill folder (plugins/revenue/skills/sales-enablement in cbrock84/headcount) into .agents/skills/sales-enablement in your project. Codex loads it when a task matches its description.
Can I use Sales Enablement 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 cbrock84/headcount --skill sales-enablement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales-enablement, .gemini/skills/sales-enablement, .github/skills/sales-enablement and .opencode/skills/sales-enablement in your project.
What does Sales Enablement need to run?
SKILL.md names no scripts, command-line tools or credentials: Sales Enablement is instructions for the agent only.
Does Sales Enablement access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sales Enablement 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 Sales Enablement use?
Sales Enablement 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 Sales Enablement use?
About 783 tokens (SKILL.md is roughly 3.1k 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 483 tokens, read only when the agent opens those files.
What are the alternatives to Sales Enablement?
Skills that share tags, products or a category with Sales Enablement: Case Study Builder (BrianRWagner/ai-marketing-claude-code-skills, 441 stars), B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars), Sales Enablement (coreyhaines31/marketingskills, 54k stars) and Eol Internal Enablement (deanpeters/Product-Manager-Skills, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sales Enablement?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.