sales-enablement

Trigger phrases

Phrases that activate this skill when typed to Claude Code:

• sales deck
• pitch deck
• one-pager
• objection handling
• demo script

What it does

sales-enablement is a Claude Code skill from Corey Haines’s marketing-skills repo. It turns Claude into a sales-enablement consultant who builds the collateral reps actually open — pitch decks structured for the buyer’s journey, one-pagers for leave-behinds, objection-handling docs by persona, demo scripts and talk tracks. The skill activates when you mention “sales deck”, “pitch deck”, “one-pager”, “objection handling”, or “demo script”.

The output of a session is a complete asset: deck (with slide-by-slide narrative arc), one-pager (with the three points reps actually need), objection-handling doc (top 10 objections with responses), or demo script with talk track and discovery questions.

When to use it

Reach for it when:

• Reps are riffing because there’s no formal deck and the message has drifted
• You’re entering a new segment and need persona-specific objection handling
• A deal-cycle review surfaced specific objections you need to address with collateral

When not to reach for it:

• The product has no clear positioning yet — sales collateral can’t manufacture story
• The problem is rep skill, not collateral; tools won’t fix that

Install

The skill is distributed via Corey Haines’s marketing-skills repo. Install via the repo’s recommended path — copy the sales-enablement SKILL.md into your project’s .claude/skills/sales-enablement/ directory, or use the repo’s plugin install if you’ve set it up.

Once installed, the skill activates on the trigger phrases above. The first time it runs, it will check for .agents/product-marketing-context.md (or .claude/product-marketing-context.md) — populating that file with your product context first dramatically improves output quality across all of Haines’s marketing skills.

What a session looks like

A typical session has three phases:

1. Asset choice + audience. Deck, one-pager, objection doc, demo script — different shapes for different jobs. The skill picks based on where in the cycle the asset gets used.
2. Narrative + structure. For decks, the slide-by-slide arc following a problem-agitation-solution structure. For objections, top 10 by persona with response patterns. For demo scripts, the discovery questions and talk track.
3. Rep-usability check. Will reps actually open this? Length, formatting, mobile readability, and the “if I had 30 seconds with the buyer” version.

The discipline that makes it work: collateral that reps don’t open is invisible. The skill optimizes for rep-usability and last-mile customization, not for being comprehensive.

Receipts

Honest reporting on what sales-enablement produces and where it has limits:

Where it works well:

• Decks structured by buyer-journey stage outperform feature-dump decks every time
• Objection-handling docs with response patterns (not memorized answers) hold up across deals
• Demo scripts with discovery questions front-loaded prevent the “demo without context” trap

Where it backfires:

• Reps need to use the collateral; rolling it out without enablement training half-fails
• Without real deal-cycle data, the objections list can be generic; pair with customer-research for real-mouth objections

Pattern that works: ship the objection-handling doc first. It’s the highest-leverage asset because it travels into every conversation, not just the structured demo.

Source and attribution

Originally written by Corey Haines. The canonical SKILL.md and any supporting files live in the sales-enablement folder of his marketing-skills repository.

License: MIT. You can install, adapt, and redistribute the skill, with attribution preserved.

This page documents the skill from a practitioner’s perspective. For the formal spec and any updates, defer to the source repo.