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-behin
Install
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill sales-enablement -a cursor -y
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,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers.
name: sales-enablement
description: "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,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. 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.4.0
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%."
Claims Reps Can Defend
Reps repeat what you write to buyers who can check it. Anything a buyer can disprove in a minute costs more than it gains.
"Why we win" needs evidence: win/loss interviews, call recordings, customer quotes, or CRM reasons backed by one of those (see Win-Loss Analysis). Without it, write advantages as hypotheses for reps to test, and say what evidence would confirm them.
Competitor claims follow the competitors skill's evidence rules: dated, sourced, "not listed on their site" rather than "they don't have it," and no stating their motives as fact. Reps can reason about why a competitor did something, labeled as a guess.
Include where you lose. A competitive doc that admits when the competitor is the better fit is one reps will trust in front of a buyer.
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
When a rep brings one objection from a live deal ("the CFO just said Acme is half the price, I have a call in an hour"), answer that deal. Don't hand back a generic doc.
Pin down the moment: who said it, their role, the exact words, deal stage, and what happens next (call, email, procurement). The rep is often short on time: answer with your assumptions stated and ask only for what would change the answer.
Name the likely concern behind it and say what in the deal points to it. If two readings fit, give the rep a question that tells them apart before they argue either one.
Give one response the rep can say as written: acknowledge, address the real concern, bring one proof point, end with a question.
Use only proof the rep can stand behind. Pull from the objection library, case studies, and battle cards. If nothing fits, say so and suggest the claim to verify. Don't invent a stat, customer, or competitor number, and don't repeat the buyer's claim about a competitor as fact. "Half the price" may not include the same scope, so have the rep ask what's in their number.
Say when not to fight. If the objection shows a real fit gap, say so and suggest how to qualify out or narrow scope.
Afterward, suggest the rep log the objection and how it went. Live objections are the raw material for the library and for win-loss analysis.
Battle Cards
A battle card is a reusable one-competitor guide for reps, used across many deals. For a single live objection, use Live Deal Objection. For public comparison pages, see competitors. Every line follows Claims Reps Can Defend.
Ask which competitor. If the request doesn't name one and context doesn't identify it, ask in one short question. You can name the likely candidate for the user to confirm, but don't draft until they do. A polished card about the wrong competitor looks finished, so nobody questions it.
Structure
When you'll see them: segments, deal sizes, and triggers where they show up
Why buyers consider them: their real appeal, in the buyer's words
Where they're strong: honest, so reps aren't blindsided
Where we win, and for whom: tied to evidence (see Claims Reps Can Defend)
Discovery questions: questions that surface the fit criteria where you're stronger, without trashing them
Top objections: with one-line responses and proof
When to walk away: deal profiles where they're the better fit
Last verified: date, and what changed since the previous version
Keeping It Current
Re-verify pricing and packaging quarterly, and whenever reps hear something new in deals.
Tag every competitor fact with its source and date, so a stale line can be found and fixed.
One page. If reps can't find the answer mid-call, cut until they can.
Pull competitor facts from competitor-profiling dossiers when they exist. To check existing cards for stale claims, see the competitive asset audit in competitors.
Win-Loss Analysis
Win-loss analysis turns CRM outcomes, call transcripts, and buyer interviews into an evidence-backed answer to "why do we win and lose, against whom?" It's the evidence that battle cards and "why we win" sections need.
Workflow
Inventory the sources and their bias: CRM loss reasons (rep-entered, skewed toward price and timing), call transcripts (what buyers said in the deal), buyer interviews (most candid, smallest sample).
Include wins. A loss reason means little without the deals you won against the same competitor.
Segment before you count. Split by competitor, segment, deal size, and stage lost. "We lose on price" across everything often hides "we lose mid-market deals to one competitor on onboarding."
Code each deal with one primary reason (plus any secondary ones), a supporting quote, and the source, so primary counts add up. Have one person code, or double-code a sample, so "primary" means the same thing throughout.
Report counts with sample sizes. "6 of 9 losses to Acme cite onboarding time" beats "onboarding is a top theme." State n every time. Small slices are directional, and under ~5 deals it's a signal to watch, not a finding.
Turn findings into assets. A deal with only a one-word CRM reason is low-confidence: confirm it with transcripts or interviews before it changes a battle card. Then update battle cards, the objection library, and discovery questions, and send product gaps to the product team.
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
Live objection
Likely concern, one response the rep can say as written, proof, follow-up question
Win-loss report
Scope, findings with counts and quotes, by-competitor breakdown, asset updates
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)
competitors: For public-facing comparison and alternative pages
competitor-profiling: For the competitor dossiers that feed battle cards
customer-research: For running buyer interviews and broader voice-of-customer research
copywriting: For marketing website copy
cold-email: For outbound prospecting emails
revops: For lead lifecycle, scoring, routing, and pipeline management
pricing: For pricing decisions and packaging
product-marketing: For foundational positioning and messaging
How do I install sales-enablement?
Download skills/sales-enablement/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does sales-enablement live?
The publisher keeps it at https://github.com/coreyhaines31/marketingskills.
Which agents can use sales-enablement?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.