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.
Build a sales enablement kit so reps can sell a product, feature, or launch confidently.
Install Sales Enablement Kit
$ npx skills add mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-enablement-kit --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sales-enablement-kit .claude/skills/sales-enablement-kit && 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-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-enablement-kit into .claude/skills/sales-enablement-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement-kit", 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/mohitagw15856/pm-claude-skills/tree/main/skills/sales-enablement-kitType 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 mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-enablement-kit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sales-enablement-kit .agents/skills/sales-enablement-kit && 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-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-enablement-kit into .agents/skills/sales-enablement-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement-kit", 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 mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-enablement-kit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sales-enablement-kit .cursor/skills/sales-enablement-kit && 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-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-enablement-kit into .cursor/skills/sales-enablement-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement-kit", 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/mohitagw15856/pm-claude-skills.git --path skills/sales-enablement-kit--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 mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-enablement-kit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sales-enablement-kit .gemini/skills/sales-enablement-kit && 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-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-enablement-kit into .gemini/skills/sales-enablement-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement-kit", 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 mohitagw15856/pm-claude-skills sales-enablement-kitInstalls 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 mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sales-enablement-kit .github/skills/sales-enablement-kit && 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-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-enablement-kit into .github/skills/sales-enablement-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement-kit", 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 mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-enablement-kit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sales-enablement-kit .opencode/skills/sales-enablement-kit && 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-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-enablement-kit into .opencode/skills/sales-enablement-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-enablement-kit", 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-kit- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 591 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a sales enablement kit so reps can sell a product, feature, or launch confidently.
- Works in 7 steps: Anchor on the buyer — name the persona,… → Compress positioning — one sentence a… → Write discovery — questions that make… → …
- Asked to create sales enablement materials
- SKILL.md covers What This Skill Produces, Required Inputs, Process and Output Format, plus 12 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sales Enablement Kit is an agent skill from mohitagw15856/pm-claude-skills. Build a sales enablement kit so reps can sell a product, feature, or launch confidently. Use when asked to create sales enablement materials, a rep-ready one-pager, talk tracks, objection handling, or a launch enablement package. Produces a complete kit — positioning summary, discovery questions, talk track, demo flow, objection handling, competitive counters, and a call-to-action for reps.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Sales enablement and Requirements gathering. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to create sales enablement materials
- A rep-ready one-pager
- Objection handling
- A launch enablement package
Example prompts
- “/sales-enablement-kit”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Anchor on the buyer — name the persona, their pain, and the outcome they buy.
- Compress positioning — one sentence a rep can say, plus 3 value pillars with proof.
- Write discovery — questions that make the pain vivid and qualify fit.
- Build the talk track — what to say at each stage; lead with value, land features as evidence.
- Map the demo — the shortest path that shows the "aha," not every screen.
- Arm for resistance — the real objections and crisp, honest counters; competitive traps and how to reframe.
- Close the loop — the CTA, next step, and links to assets.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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 Kit loads about 1.1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 591 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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 591 words, ~1,136 tokens.
Download SKILL.mdSave it as
.claude/skills/sales-enablement-kit/SKILL.md (or your agent's skills folder).- name
- sales-enablement-kit
- description
- Build a sales enablement kit so reps can sell a product, feature, or launch confidently. Use when asked to create sales enablement materials, a rep-ready one-pager, talk tracks, objection handling, or a launch enablement package. Produces a complete kit — positioning summary, discovery questions, talk track, demo flow, objection handling, competitive counters, and a call-to-action for reps.
Sales Enablement Kit Skill
Give reps everything they need to have a confident, on-message conversation about a product or launch — without reading a 40-page deck. The kit should be skimmable, specific, and usable live on a call.
What This Skill Produces
- A one-screen positioning summary reps can internalize fast
- Discovery questions that surface the pain this product solves
- A talk track and demo flow tied to buyer value, not features
- Objection handling and competitive counters
- Clear next steps and where to find assets
Required Inputs
Ask for these if not provided:
- What's being sold — product, feature, or launch, and who it's for (segment, persona, buyer vs user)
- The core value — the problem it solves and the measurable outcome
- Proof — customers, metrics, case studies, or a demo environment
- Top competitors and the main objections reps hear today
- Pricing/packaging basics and any constraints on what reps can say
- The motion — inbound, outbound, PLG-assist, partner
Mark anything unknown as [to confirm] rather than inventing claims or metrics.
Process
- Anchor on the buyer — name the persona, their pain, and the outcome they buy.
- Compress positioning — one sentence a rep can say, plus 3 value pillars with proof.
- Write discovery — questions that make the pain vivid and qualify fit.
- Build the talk track — what to say at each stage; lead with value, land features as evidence.
- Map the demo — the shortest path that shows the "aha," not every screen.
- Arm for resistance — the real objections and crisp, honest counters; competitive traps and how to reframe.
- Close the loop — the CTA, next step, and links to assets.
Output Format
Sales Enablement Kit — [Product / Launch]
For: [Segment · persona · buyer] · Motion: [inbound/outbound/PLG] · Status: [GA / beta]
The 10-Second Pitch
[One sentence a rep can deliver verbatim.]
Who It's For & Why They Care
- Persona: [role] · Pain: [what hurts today] · Outcome: [measurable result]
Value Pillars
| Pillar | What it means to the buyer | Proof |
|---|---|---|
| [Pillar] | [buyer-language benefit] | [metric / customer / demo step] |
Discovery Questions
- [Question that surfaces the pain]
- [Question that quantifies impact]
- [Question that qualifies fit / timing / budget]
Talk Track
- Opening: [value-led framing]
- Deepen: [tie pain to pillar]
- Evidence: [proof point]
Show full SKILL.md (232 more words)Show less
Demo Flow (shortest path to "aha")
- [Setup — the before state]
- [The key moment — the payoff]
- [Expand — one adjacent value]
Objection Handling
| Objection | Honest response | Reframe |
|---|---|---|
| [Objection] | [acknowledge + answer] | [move the conversation forward] |
Competitive Counters
- vs [Competitor]: [where we win] · Trap to avoid: [what not to claim]
Next Step & Assets
- CTA: [the specific next step to ask for]
- Assets: [deck, one-pager, case study, demo env — or
[to confirm]]
Quality Checks
- The 10-second pitch is one sentence and jargon-free
- Every value pillar has a proof point, or is marked
[to confirm] - Discovery questions surface pain, not product features
- The demo flow is the shortest path to the payoff, not a tour
- Objection responses are honest — they don't over-claim
- A new rep could run a call from this kit alone
Anti-Patterns
- Do not list every feature; reps sell outcomes, not spec sheets
- Do not invent metrics, logos, or case studies — mark them
[to confirm] - Do not write objection answers that dodge the real concern
- Do not make the demo a full product tour; find the one "aha"
- Do not bury the CTA — reps need to know exactly what to ask for next
Example Trigger Phrases
- "Build a sales enablement kit for our new [feature] launch"
- "Write a rep-ready one-pager with talk track and objection handling"
- "Create discovery questions and a demo flow for [product]"
- "Arm the sales team to sell against [Competitor]"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/sales-enablement-kit of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Sales Enablement Kit 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 Kit this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | 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 mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Sales Enablement Kit
What does Sales Enablement Kit do?
Build a sales enablement kit so reps can sell a product, feature, or launch confidently. Sales Enablement Kit is an agent skill from mohitagw15856/pm-claude-skills. Build a sales enablement kit so reps can sell a product, feature, or launch confidently.
When should I use Sales Enablement Kit?
Sales Enablement Kit fits situations like: asked to create sales enablement materials; A rep-ready one-pager; objection handling; A launch enablement package.
How do I install Sales Enablement Kit in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a claude-code`. Or copy the skill folder (skills/sales-enablement-kit in mohitagw15856/pm-claude-skills) into .claude/skills/sales-enablement-kit in your project. Claude Code loads it when a task matches its description.
How do I install Sales Enablement Kit in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a codex`. Or copy the skill folder (skills/sales-enablement-kit in mohitagw15856/pm-claude-skills) into .agents/skills/sales-enablement-kit in your project. Codex loads it when a task matches its description.
Can I use Sales Enablement Kit 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 mohitagw15856/pm-claude-skills --skill sales-enablement-kit -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-kit, .gemini/skills/sales-enablement-kit, .github/skills/sales-enablement-kit and .opencode/skills/sales-enablement-kit in your project.
What does Sales Enablement Kit need to run?
SKILL.md names no scripts, command-line tools or credentials: Sales Enablement Kit is instructions for the agent only.
Does Sales Enablement Kit 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 Kit 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 Kit use?
Sales Enablement Kit 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 Kit use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sales Enablement Kit?
Skills that share tags, products or a category with Sales Enablement Kit: 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 Kit?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.