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]
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
Anti-Patterns
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]"
1---2name: sales-enablement-kit-23description: "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."4homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/sales-enablement-kit.html5metadata:6 source: https://skillmd.com/skills/mohitagw15856/sales-enablement-kit-27 openclaw:8 emoji: 📣9---1011# Sales Enablement Kit Skill1213Give 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.1415## What This Skill Produces1617- A one-screen positioning summary reps can internalize fast18- Discovery questions that surface the pain this product solves19- A talk track and demo flow tied to buyer value, not features20- Objection handling and competitive counters21- Clear next steps and where to find assets2223## Required Inputs2425Ask for these if not provided:2627- **What's being sold** — product, feature, or launch, and who it's for (segment, persona, buyer vs user)28- **The core value** — the problem it solves and the measurable outcome29- **Proof** — customers, metrics, case studies, or a demo environment30- **Top competitors** and the main objections reps hear today31- **Pricing/packaging** basics and any constraints on what reps can say32- **The motion** — inbound, outbound, PLG-assist, partner3334Mark anything unknown as `[to confirm]` rather than inventing claims or metrics.3536## Process37381. **Anchor on the buyer** — name the persona, their pain, and the outcome they buy.392. **Compress positioning** — one sentence a rep can say, plus 3 value pillars with proof.403. **Write discovery** — questions that make the pain vivid and qualify fit.414. **Build the talk track** — what to say at each stage; lead with value, land features as evidence.425. **Map the demo** — the shortest path that shows the "aha," not every screen.436. **Arm for resistance** — the real objections and crisp, honest counters; competitive traps and how to reframe.447. **Close the loop** — the CTA, next step, and links to assets.4546## Output Format4748---4950# Sales Enablement Kit — [Product / Launch]5152**For:** [Segment · persona · buyer] · **Motion:** [inbound/outbound/PLG] · **Status:** [GA / beta]5354## The 10-Second Pitch55[One sentence a rep can deliver verbatim.]5657## Who It's For & Why They Care58- **Persona:** [role] · **Pain:** [what hurts today] · **Outcome:** [measurable result]5960## Value Pillars61| Pillar | What it means to the buyer | Proof |62|---|---|---|63| [Pillar] | [buyer-language benefit] | [metric / customer / demo step] |6465## Discovery Questions661. [Question that surfaces the pain]672. [Question that quantifies impact]683. [Question that qualifies fit / timing / budget]6970## Talk Track71- **Opening:** [value-led framing]72- **Deepen:** [tie pain to pillar]73- **Evidence:** [proof point]7475## Demo Flow (shortest path to "aha")761. [Setup — the before state]772. [The key moment — the payoff]783. [Expand — one adjacent value]7980## Objection Handling81| Objection | Honest response | Reframe |82|---|---|---|83| [Objection] | [acknowledge + answer] | [move the conversation forward] |8485## Competitive Counters86- **vs [Competitor]:** [where we win] · **Trap to avoid:** [what not to claim]8788## Next Step & Assets89- **CTA:** [the specific next step to ask for]90- **Assets:** [deck, one-pager, case study, demo env — or `[to confirm]`]9192---9394## Quality Checks9596- [ ] The 10-second pitch is one sentence and jargon-free97- [ ] Every value pillar has a proof point, or is marked `[to confirm]`98- [ ] Discovery questions surface pain, not product features99- [ ] The demo flow is the shortest path to the payoff, not a tour100- [ ] Objection responses are honest — they don't over-claim101- [ ] A new rep could run a call from this kit alone102103## Anti-Patterns104105- [ ] Do not list every feature; reps sell outcomes, not spec sheets106- [ ] Do not invent metrics, logos, or case studies — mark them `[to confirm]`107- [ ] Do not write objection answers that dodge the real concern108- [ ] Do not make the demo a full product tour; find the one "aha"109- [ ] Do not bury the CTA — reps need to know exactly what to ask for next110111## Example Trigger Phrases112113- "Build a sales enablement kit for our new [feature] launch"114- "Write a rep-ready one-pager with talk track and objection handling"115- "Create discovery questions and a demo flow for [product]"116- "Arm the sales team to sell against [Competitor]"