Agent skill

sales-enablement-kit

Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived from the PR-FAQ spine, an objection-handling table (objection → response → evidence), internal FAQ + CS macros, and an internal launch announcement with embargo discipline. Not for the external message house — use message-house-builder; not for competitor tracking itself — use comp

aaron-he-zhu2,508★ · 1 repos on radarProfile →
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill sales-enablement-kit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: launch/assemble/sales-enablement-kit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Sales Enablement Kit Derives the internal enablement kit for a **sales-led** launch — battle cards, a sales talk track, an objection-handling table, internal FAQ + CS macros, and the internal launch announcement — from the message house and PR-FAQ spine, so that sales, support, and CS say the same true thing the launch says publicly. It sits in the Assemble phase of the [RAMP loop](../../../references/ramp-benchmark.md) and feeds two sub-items: the `A`-dimension enablement sub-item (sales/support enablement ready where sales-led) and the `R`-dimension internal-readiness sub-item (support/sales/CS briefed, owners + escalation path). It never originates a fact: every card, response, and macro traces back to the message house, the claims ledger, or a named competitor source. **Scope guard**: this skill builds *internal* enablement material only. It does **not** write the external message house or PR-FAQ ([message-house-builder](../message-house-builder/SKILL.md) is the only source of external messaging facts — this skill derives, never adds), track competitors itself (that is [competitor-tracker](../../../influencer/target/competitor-tracker/SKILL.md) for ongoing partnership/activit

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Save Results
  7. Reference Materials
  8. Next Best Skill
More from aaron-marketing-skills
All skills →
About this skill
What does the sales-enablement-kit skill do?

Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived from the PR-FAQ spine, an objection-handling table (objection → response → evidence), internal FAQ + CS macros, and an internal launch announcement with embargo discipline. Not for the external message house — use message-house-builder; not for competitor tracking itself — use comp

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill sales-enablement-kit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going