Agent Skillsmohitagw15856/pm-claude-skills › sales-enablement-kit

sales-enablement-kit

GitHub

为销售团队构建赋能套件,包含定位摘要、发现性问题、话术、演示流程、异议处理及竞争对策。通过结构化输出帮助代表自信销售产品或发布活动,确保内容精简且实战可用。

plugins/pm-pmm/skills/sales-enablement-kit/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

创建销售赋能材料 生成代表就绪的一页纸指南 编写话术和异议处理策略 制作发布活动赋能包

Install

npx skills add mohitagw15856/pm-claude-skills --skill sales-enablement-kit -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/plugins/pm-pmm/skills/sales-enablement-kit -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@sales-enablement-kit

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill sales-enablement-kit -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "sales-enablement-kit",
    "description": "Build a sales enablement kit so reps can sell a product, feature, or launch confidently. Use when asked to create sales enablement materials, a rep-ready one-pager, talk tracks, objection handling, or a launch enablement package. Produces a complete kit — positioning summary, discovery questions, talk track, demo flow, objection handling, competitive counters, and a call-to-action for reps."
}

Sales Enablement Kit Skill

Give reps everything they need to have a confident, on-message conversation about a product or launch — without reading a 40-page deck. The kit should be skimmable, specific, and usable live on a call.

What This Skill Produces

  • A one-screen positioning summary reps can internalize fast
  • Discovery questions that surface the pain this product solves
  • A talk track and demo flow tied to buyer value, not features
  • Objection handling and competitive counters
  • Clear next steps and where to find assets

Required Inputs

Ask for these if not provided:

  • What's being sold — product, feature, or launch, and who it's for (segment, persona, buyer vs user)
  • The core value — the problem it solves and the measurable outcome
  • Proof — customers, metrics, case studies, or a demo environment
  • Top competitors and the main objections reps hear today
  • Pricing/packaging basics and any constraints on what reps can say
  • The motion — inbound, outbound, PLG-assist, partner

Mark anything unknown as [to confirm] rather than inventing claims or metrics.

Process

  1. Anchor on the buyer — name the persona, their pain, and the outcome they buy.
  2. Compress positioning — one sentence a rep can say, plus 3 value pillars with proof.
  3. Write discovery — questions that make the pain vivid and qualify fit.
  4. Build the talk track — what to say at each stage; lead with value, land features as evidence.
  5. Map the demo — the shortest path that shows the "aha," not every screen.
  6. Arm for resistance — the real objections and crisp, honest counters; competitive traps and how to reframe.
  7. Close the loop — the CTA, next step, and links to assets.

Output Format


Sales Enablement Kit — [Product / Launch]

For: [Segment · persona · buyer] · Motion: [inbound/outbound/PLG] · Status: [GA / beta]

The 10-Second Pitch

[One sentence a rep can deliver verbatim.]

Who It's For & Why They Care

  • Persona: [role] · Pain: [what hurts today] · Outcome: [measurable result]

Value Pillars

Pillar What it means to the buyer Proof
[Pillar] [buyer-language benefit] [metric / customer / demo step]

Discovery Questions

  1. [Question that surfaces the pain]
  2. [Question that quantifies impact]
  3. [Question that qualifies fit / timing / budget]

Talk Track

  • Opening: [value-led framing]
  • Deepen: [tie pain to pillar]
  • Evidence: [proof point]

Demo Flow (shortest path to "aha")

  1. [Setup — the before state]
  2. [The key moment — the payoff]
  3. [Expand — one adjacent value]

Objection Handling

Objection Honest response Reframe
[Objection] [acknowledge + answer] [move the conversation forward]

Competitive Counters

  • vs [Competitor]: [where we win] · Trap to avoid: [what not to claim]

Next Step & Assets

  • CTA: [the specific next step to ask for]
  • Assets: [deck, one-pager, case study, demo env — or [to confirm]]

Quality Checks

  • The 10-second pitch is one sentence and jargon-free
  • Every value pillar has a proof point, or is marked [to confirm]
  • Discovery questions surface pain, not product features
  • The demo flow is the shortest path to the payoff, not a tour
  • Objection responses are honest — they don't over-claim
  • A new rep could run a call from this kit alone

Anti-Patterns

  • Do not list every feature; reps sell outcomes, not spec sheets
  • Do not invent metrics, logos, or case studies — mark them [to confirm]
  • Do not write objection answers that dodge the real concern
  • Do not make the demo a full product tour; find the one "aha"
  • Do not bury the CTA — reps need to know exactly what to ask for next

Example Trigger Phrases

  • "Build a sales enablement kit for our new [feature] launch"
  • "Write a rep-ready one-pager with talk track and objection handling"
  • "Create discovery questions and a demo flow for [product]"
  • "Arm the sales team to sell against [Competitor]"

Version History

  • a38bc30 Current 2026-07-05 11:25

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
eb164690
Indexed
2026-07-05 11:25

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 16:59
浙ICP备14020137号-1 $방문자$