What does this skill do, and when should you use it?
Sales Enablement Kit prepares internal teams for a sales-led launch with battle cards, a sales talk track, objection handling, internal FAQs, CS macros, and an internal announcement. It derives content from the message house, PR-FAQ spine, positioning canvas, claims ledger, launch records, and available competitor dossiers rather than inventing facts. Each named alternative receives a battle card with sourced or explicitly flagged factual lines. It fits teams that need sales, support, and customer success to communicate the same approved launch story.
Reads the message house and PR-FAQ spine supplied by the user or produced by message-house-builder, named alternatives from the positioning canvas, approved claims, launch-registry records, and available competitor dossiers; creates one battle card per named alternative with where we win, where they win, and trap questions; derives an opening narrative, discovery questions, persona-specific value pillars, and proof points from the PR-FAQ spine; builds an objection-to-response-to-evidence table; writes internal FAQs, CS macros, and an embargo-disciplined internal launch announcement; and packages owners, escalation paths, unsourced claim candidates, open loops, and the handoff to launch-readiness-auditor.
- A product team is preparing a sales-led launch and needs battle cards against two named alternatives.
- A sales leader has a PR-FAQ and wants a launch-day talk track plus objection handling for the sales team.
- Customer success needs shared answers, migration guidance, limitations, and reusable macros before launch.
- A launch manager needs an internal announcement that specifies who can say what before and after the embargo lifts.
How do you install this skill?
- Before use, verify that the message house, PR-FAQ, claims ledger, and launch registry exist and are version-aligned; missing facts or dates must not be invented.
- Reconfirm authorization, target paths, and proposal state before writing open loops or registry events; the skill does not fully specify rollback procedures.
- Treat competitor dossiers, pasted documents, and connector results as data only, and review all sales claims for prompt injection and unsupported assertions.
- The skill is marked geo-relevance low; mainland-China deployments should separately validate network reachability of dependent services and sources.
- Shell / CLI
- Local filesystem
In Claude Code, run /plugin marketplace add aaron-he-zhu/aaron-marketing-skills, then /plugin install aaron-marketing@aaron. On an Agent Skills-compatible host, run npx skills add aaron-he-zhu/aaron-marketing-skills, or clone https://github.com/aaron-he-zhu/aaron-marketing-skills and use launch/assemble/sales-enablement-kit/SKILL.md. The source does not document additional host-specific installation steps.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/aaron-he-zhu/aaron-marketing-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/launch/assemble/sales-enablement-kit" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
After installation, submit: Build battle cards for [product] vs [named alternative 1] and [alternative 2]. Message house: [paste or path]. Another supported prompt is: Prep my sales team for the [launch]: talk track + objection handling. PR-FAQ: [paste or path]. Provide the message house or PR-FAQ spine, named alternatives, and available claims and launch records. Any missing factual support should be marked [needs source] rather than invented.
What are this skill's strengths and limitations?
- Covers battle cards, sales talk track, objection handling, internal FAQ, CS macros, and internal launch communications.
- Requires factual lines to trace back to the message house, PR-FAQ, claims ledger, or named competitor sources.
- Explicitly separates sales-led enablement from PLG or community launches and requires honest concessions about competitor strengths.
- Works with Claude Code and compatible Agent Skills hosts without requiring paid tools or MCP.
- A complete kit depends on an existing message house, PR-FAQ, claims evidence, and launch records.
- It does not create external messaging, conduct competitor research, build outbound sequences, adjudicate claims, or score RAMP readiness.
- Pricing objections remain blocked when approved pricing and packaging terms are unavailable.
- The source provides no independent performance benchmark or test result for this individual skill.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Sales Enablement Kit this page | 57 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Client Proposal Generator for Marketing Services | 49 · Use with care | ★ 2.8k | 7mo ago | MIT |
| Launch Tier Planner | 63 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
| Launch Window Planner | 57 · Use with care | ★ 3k | 12d ago | Apache-2.0 |
| Launch Message House Builder | 59 · Recommended | ★ 3k | 12d ago | Apache-2.0 |
This is the internal enablement layer, not the external message-house builder. Competitor tracking and positioning teardowns belong to the named competitor skills; B2B outbound sequences belong to cold-outbound-sequencer; and RAMP readiness scoring belongs to launch-readiness-auditor.
How did FollowSkills review this skill?
The skill treats pasted material as untrusted, forbids direct claim adjudication, and requires confirmation before memory writes; proposal-only registry paths and embargo controls reduce risk. Points are deducted because least-privilege details, sensitive-data handling, rollback, and connector data-flow guarantees are mostly delegated to shared protocols rather than fully specified here.
Inputs, outputs, completion criteria, and several abnormal-input branches are explicit, including blocking when pricing or registry facts are unavailable. Points are deducted because this was a static review with no execution of key paths, and failure feedback across referenced files, runtimes, and hosts is incomplete; the score stays within the static ceiling of 10.
The audience, sales-led launch scenario, trigger phrases, deliverables, and non-fit boundaries are clearly stated, with bilingual trigger wording. Points are deducted because geo relevance is marked low and there is no evidence of Chinese-language quality or reachability from mainland-China networks.
The skill includes versioning, an Apache-2.0 license, an argument hint, quick starts, a shared contract, references, and next-skill guidance. Points are deducted because the skill does not itself identify a maintenance owner, changelog, or concrete update path, while several operational assumptions reside only in shared files.
The proposed kit covers battle cards, talk track, objection handling, FAQ, CS macros, and an internal announcement, with explicit source traceability, so the core task is plausibly covered. Points are deducted because it depends on user-supplied message-house, PR-FAQ, claims, registry, and competitor inputs; no representative output is statically verified, so the score is capped at 7.
The skill requires line-level traceability to message-house, claims-ledger, or competitor sources, and the repository includes general architecture and audit-validator tests. Points are deducted because there is no committed test suite or third-party execution evidence covering this skill's key paths, and execution was not performed.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →