When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers.
metadata
{"version":"2.0.1"}
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):
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?
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
Collateral Needs
What specific assets do you need?
What stage of the funnel are they for?
Who will use them? (AE, SDR, champion, prospect)
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
Current World Problem โ The pain your buyer lives with today
Cost of the Problem โ What inaction costs (time, money, risk)
The Shift Happening โ Market or technology change creating urgency
Your Approach โ How you solve it differently
Product Walkthrough โ 3-4 key workflows, not a feature tour
New product launch โ Reps need a single source of truth
New market segment โ Different buyers need different approaches
New hire ramp โ Playbooks cut ramp time significantly
Keeping It Living
Playbooks die when they're not updated. Review quarterly, get input from top reps, and remove anything outdated. Assign an owner โ if nobody owns it, it rots.
Buyer Persona Cards
Card Structure
Field
Description
Role / title
Common titles and reporting structure
Goals
What success looks like for them
Pains
What frustrates them daily
Top objections
The 3-5 objections you'll hear from this role
Evaluation criteria
How they judge solutions
Buying process
Their role in the decision, who they influence
Messaging angle
The one sentence that resonates most
Persona Types
Economic buyer โ Signs the check. Cares about ROI and risk.
Technical buyer โ Evaluates the product. Cares about capabilities and integration.
End user โ Uses it daily. Cares about ease and workflow fit.
Champion โ Advocates internally. Needs ammunition to sell for you.
Blocker โ Opposes the purchase. Understand their concern to neutralize it.
Output Format
Deliver the right format for each asset type:
Asset
Deliverable
Sales deck
Slide-by-slide outline with headline, body copy, and speaker notes
One-pager
Full copy with layout guidance (visual hierarchy, sections)
Objection doc
Table format: objection, response, proof point, follow-up
Demo script
Scene-by-scene with timing, talk track, and interaction points
ROI calculator
Input fields, formulas, output display with sample data
Playbook
Structured document with table of contents and sections
Persona card
One-page card format per persona
Proposal
Section-by-section copy with customization notes
Task-Specific Questions
If context is missing, ask:
What collateral do you need? (deck, one-pager, objection doc, etc.)
Who will use it? (AE, SDR, champion, prospect)
What sales stage is it for? (prospecting, discovery, demo, negotiation, close)
Who is the target persona? (title, seniority, department)
