Sales Enablement
Produce pitch decks, one-pagers, objection guides, demo scripts, and playbooks your reps actually use on live deals.
Overview
Sales Enablement is an agent skill most often used in Grow (also Validate, Launch) that creates B2B sales collateral—decks, one-pagers, objection docs, demo scripts, and playbooks—so reps can close deals with consistent
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill sales-enablementWhat is this skill?
- Drafts pitch decks, one-pagers, leave-behinds, and proposal templates from product marketing context
- Builds objection-handling docs and deal-specific ROI narratives aligned to buyer personas
- Produces demo scripts, talk tracks, and sales playbooks reps can run in calls
- Reads `.agents/product-marketing.md` (or legacy paths) before re-asking positioning questions
- Routes competitor battle cards to competitors skill and site copy to copywriting or cold-email skills
Adoption & trust: 58.5k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a working product but reps improvise decks and answers on every call, so deals stall on unclear ROI and inconsistent positioning.
Who is it for?
Founders doing founder-led sales or enabling a tiny sales team with repeatable decks, objections, and demo scripts.
Skip if: Pure marketing homepage rewrites, cold outbound sequences, or deep competitive intelligence pages—use copywriting, cold-email, or competitors instead.
When should I use this skill?
User wants sales collateral, pitch decks, one-pagers, objection handling, demo scripts, talk tracks, playbooks, proposal templates, buyer persona cards, or asks to help their sales team.
What do I get? / Deliverables
You get structured sales assets grounded in your value prop and personas, ready to attach to opportunities or train new sellers on a repeatable talk track.
- Pitch deck or slide outline
- One-pager or leave-behind
- Objection-handling and demo script documents
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow because the outputs are post-product sales collateral that compounds pipeline and close rates, not one-off website copy. Content is the right facet for decks, leave-behinds, talk tracks, and buyer-facing enablement assets rather than analytics or support ops.
Where it fits
Turn validated pricing and outcomes into a one-pager reps can send after discovery calls.
Package a launch narrative into a pitch deck for channel partners or early enterprise pilots.
Refresh objection docs and demo scripts after you add features mid-quarter.
Align talk tracks with expansion and renewal motions for existing accounts.
How it compares
Use for rep-facing deal collateral, not for landing-page conversion audits like a dedicated page CRO workflow.
Common Questions / FAQ
Who is sales-enablement for?
Solo founders and indie teams selling B2B who need pitch materials, objection handling, and demo scripts without hiring a full sales ops function.
When should I use sales-enablement?
Use it in Validate when sharpening positioning for early sales conversations, in Launch when packaging a narrative for partners or field reps, and in Grow whenever you need playbooks, one-pagers, or deal-specific ROI docs—as triggered by terms like sales deck, talk track, or sale
Is sales-enablement safe to install?
It is prose workflow guidance with no built-in shell or network tools in the skill itself; review the Security Audits panel on this Prism page before trusting any third-party skill package.
SKILL.md
READMESKILL.md - Sales Enablement
# Sales Enablement You are an expert in B2B sales enablement. Your goal is to create sales collateral that reps actually use — decks, one-pagers, objection docs, demo scripts, and playbooks that help close deals. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): 1. **Value Proposition & Differentiators** - What do you sell and who is it for? - What makes you different from the next best alternative? - What outcomes can you prove? 2. **Sales Motion** - How do you sell? (self-serve, inside sales, field sales, hybrid) - Average deal size and sales cycle length - Key personas involved in the buying decision 3. **Collateral Needs** - What specific assets do you need? - What stage of the funnel are they for? - Who will use them? (AE, SDR, champion, prospect) 4. **Current State** - What materials exist today? - What's working and what's not? - What do reps ask for most? --- ## Core Principles ### Sales Uses What Sales Trusts Involve reps in creation. Use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with your top performers first. ### Situation-Specific, Not Generic Tailor to persona, deal stage, and use case. A deck for a CTO should look different from one for a VP of Sales. A one-pager for post-meeting follow-up serves a different purpose than one for a trade show. ### Scannable Over Comprehensive Reps need information in 3 seconds, not 30. Use bold headers, short bullets, and visual hierarchy. If a rep can't find the answer mid-call, the doc has failed. ### Tie Back to Business Outcomes Every claim connects to revenue, efficiency, or risk reduction. Features mean nothing without the "so what." Replace "AI-powered analytics" with "cut reporting time by 80%." --- ## Sales Deck / Pitch Deck ### 10-12 Slide Framework 1. **Current World Problem** — The pain your buyer lives with today 2. **Cost of the Problem** — What inaction costs (time, money, risk) 3. **The Shift Happening** — Market or technology change creating urgency 4. **Your Approach** — How you solve it differently 5. **Product Walkthrough** — 3-4 key workflows, not a feature tour 6. **Proof Points** — Metrics, logos, analyst recognition 7. **Case Study** — One customer story told well 8. **Implementation / Timeline** — How they get from here to live 9. **ROI / Value** — Expected return and payback period 10. **Pricing Overview** — Transparent, tiered if applicable 11. **Next Steps / CTA** — Clear action with timeline ### Deck Principles - **Story arc, not feature tour.** Every deck tells a story: the world has a problem, there's a better way, here's proof, here's how to get there. - **One idea per slide.** If you need two points, use two slides. - **Design for presenting, not reading.** Slides support the conversation — they don't replace it. Minimal text, strong visuals. ### Customization by Buyer Type | Buy