Create comprehensive sales playbooks for products, segments, or sales motions. Use this skill whenever someone needs to build a sales playbook, create a new hire onboarding guide, document a sales process, standardize a sales motion, says "build a playbook for [product/segment]", "document our sales process", "create a selling guide", or when systematizing tribal knowledge into repeatable processes. Also trigger when someone mentions sales methodology documentation, go-to-market playbooks, vertical playbooks, or rep enablement guides.
Creates structured sales playbooks by analyzing CRM, Gong, and sales intelligence data to document repeatable winning processes.
/plugin marketplace add https://www.claudepluginhub.com/api/plugins/jbalbu01-sales-enablement-2/marketplace.json/plugin install jbalbu01-sales-enablement-2@cpd-jbalbu01-sales-enablement-2This skill inherits all available tools. When active, it can use any tool Claude has access to.
Create structured, actionable sales playbooks that turn your best reps' knowledge into a repeatable system the whole team can follow. A playbook isn't a PDF that sits on a shelf — it's a living reference that reps actually use in their day-to-day work.
┌─────────────────────────────────────────────────────────────────┐
│ PLAYBOOK BUILDER │
├─────────────────────────────────────────────────────────────────┤
│ PLAYBOOK TYPES │
│ 1. Product Playbook — How to sell a specific product │
│ 2. Segment Playbook — How to sell into a specific vertical │
│ 3. Motion Playbook — Inbound, outbound, expansion, etc. │
│ 4. Competitive Playbook — How to win against specific rivals │
│ 5. New Hire Playbook — Everything a new rep needs to ramp │
├─────────────────────────────────────────────────────────────────┤
│ DELIVERY │
│ • Structured markdown (copy-paste, wiki-ready) │
│ • Word document for formal distribution │
│ • Interactive HTML with collapsible sections │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Win/loss patterns, deal metrics, stage analysis │
│ + ~~CRM: Rep performance data for best-practice extraction │
│ + ~~CRM: ICP validation from won deal profiles │
│ + ~~conversation intelligence (Gong): Top rep call patterns │
│ + ~~conversation intelligence (Gong): Discovery question bank │
│ + ~~conversation intelligence (Gong): Objection frequency data │
│ + ~~data enrichment (ZoomInfo): ICP company validation │
│ + ~~data enrichment (ZoomInfo): Competitive tech stack intel │
│ + ~~data enrichment (LinkedIn): Buyer persona validation │
│ + ~~chat: Internal tribal knowledge and rep feedback │
└─────────────────────────────────────────────────────────────────┘
CRITICAL: Before asking for tribal knowledge, pull every data point from connected tools. The best playbooks are grounded in actual win patterns, not theory.
Check if you have access to CRM tools (look for tools containing search_crm_objects, get_crm_objects, or similar).
If CRM tools ARE available:
dealname, amount, dealstage, closedate, createdate, pipeline, hubspot_owner_id, dealtype, description, closed_lost_reason, closed_won_reasonname, industry, numberofemployees, annualrevenuefirstname, lastname, jobtitle, emailsearch_owners to identify top performers.
Check if you have access to Gong tools (look for tools prefixed with gong_).
If Gong tools ARE available:
gong_search_calls_by_participant + gong_get_call_stats for reps with highest win rates.
gong_get_transcript on 3-5 top-performer discovery calls.
gong_search_calls with objection keywords.
gong_get_call_details to find competitor mentions.
ZoomInfo (if available):
zoominfo_search_company on won deal companies to verify company profiles.
zoominfo_get_tech_stack on won and lost deal companies.
LinkedIn (if available):
linkedin_search_leads for champion titles from won deals.
If chat tools are available:
"I analyzed [N] deals from the last [period] — [N] won at [X]% win rate with $[X] avg deal size and [X]-day avg cycle. Top loss reasons: [reason 1], [reason 2]. Per CRM, your best customers are [size] [industry] companies, and your typical buying committee includes [titles]. [If Gong:] Top performers have a [X:Y] talk ratio and ask [N] questions per call. Building your data-driven playbook now..."
After the auto-pull, ask ONLY for what the tools couldn't provide:
Build using ALL evidence. Mark data-sourced sections: "Per CRM ([N] deals):", "Per Gong (top 5 reps):", "Per ZoomInfo:", "Per Slack:" The playbook should be grounded in what actually works, not generic frameworks.
memory/product.md with product positioning documented in the playbookmemory/deal-patterns.md with patterns discovered during analysismemory/competitors.md with competitive intelligence surfacedmemory/content-registry.mdmemory/changelog.mdThe more context you provide, the more specific and useful the playbook:
I'll supplement with research and proven frameworks, but your team's actual experience is the most valuable input.
# Sales Playbook: [Product Name]
**Version:** [X.0]
**Last Updated:** [Date]
**Owner:** [Name/Team]
---
## Quick Reference
| | Detail |
|---|---|
| **Product** | [Name and one-line description] |
| **ICP** | [Company size, industry, characteristics] |
| **Primary Persona** | [Title and description] |
| **Average Deal Size** | $[X] |
| **Average Sales Cycle** | [X] weeks/months |
| **Win Rate** | [X]% |
| **Top Competitors** | [List] |
---
## Ideal Customer Profile
### Company Characteristics
- **Size:** [Employee count and/or revenue range]
- **Industry:** [Verticals where you win most]
- **Signals:** [Events/triggers that indicate a good fit]
- **Disqualifiers:** [Red flags that mean bad fit]
### Buying Committee
| Role | Priority | What They Care About | How to Engage |
|------|----------|---------------------|---------------|
| [Title] | Champion | [Their priorities] | [Approach] |
| [Title] | Decision Maker | [Their priorities] | [Approach] |
| [Title] | Influencer | [Their priorities] | [Approach] |
| [Title] | Blocker | [Their concerns] | [How to neutralize] |
---
## Value Proposition
### Elevator Pitch (30 seconds)
> "[Scripted pitch that any rep can use]"
### By Persona
**For [Persona 1]:**
> "[Tailored message focused on their priorities]"
**For [Persona 2]:**
> "[Tailored message]"
### Key Value Drivers
1. **[Driver 1]** — [Supporting evidence, customer quote, data point]
2. **[Driver 2]** — [Evidence]
3. **[Driver 3]** — [Evidence]
---
## Sales Process
### Stage 1: [Prospecting/Outreach]
**Goal:** [What you're trying to achieve]
**Activities:**
- [Activity 1]
- [Activity 2]
**Exit Criteria:** [What must be true to advance]
**Tools/Resources:** [What to use]
### Stage 2: [Discovery]
**Goal:** [Goal]
**Key Questions:** [Top 5 questions]
**Exit Criteria:** [Qualification gates]
**Common Mistakes:** [What to avoid]
### Stage 3: [Demo/Presentation]
**Goal:** [Goal]
**Demo Flow:** [Recommended structure]
**Personalization Points:** [How to tailor]
**Exit Criteria:** [Next step commitment]
### Stage 4: [Proposal/Business Case]
**Goal:** [Goal]
**Proposal Template:** [Link or reference]
**Pricing Guidance:** [How to present pricing]
**Exit Criteria:** [Verbal commitment]
### Stage 5: [Negotiation/Close]
**Goal:** [Goal]
**Negotiation Guardrails:** [What you can/can't flex on]
**Common Objections:** [Top 3 with responses]
**Close Techniques:** [What works for this product]
---
## Objection Handling Quick Reference
| Objection | Category | Response |
|-----------|----------|----------|
| "[Objection 1]" | Price | [Brief response] |
| "[Objection 2]" | Timing | [Brief response] |
| "[Objection 3]" | Competition | [Brief response] |
| "[Objection 4]" | Need | [Brief response] |
---
## Competitive Positioning
### vs [Competitor A]
**We win when:** [Scenario]
**We lose when:** [Scenario]
**Key differentiator:** [What to lead with]
**Landmine question:** "[Question that exposes their weakness]"
### vs [Competitor B]
[Same structure]
### vs Status Quo (No Decision)
**We win when:** [What creates urgency]
**We lose when:** [Why they stick with current state]
**Key argument:** [Cost of inaction]
---
## Discovery Question Bank
### Situation
1. [Question]
2. [Question]
### Problem
1. [Question]
2. [Question]
### Implication
1. [Question]
2. [Question]
### Need-Payoff
1. [Question]
2. [Question]
---
## Email Templates
### Initial Outreach
**Subject:** [Template]
**Body:** [Template with personalization markers]
### Post-Discovery Follow-Up
**Subject:** [Template]
**Body:** [Template]
### Proposal Send
**Subject:** [Template]
**Body:** [Template]
---
## Success Stories
### [Customer Name]
**Situation:** [Brief context]
**Challenge:** [What was broken]
**Solution:** [What you provided]
**Result:** [Quantified outcome]
**Quote:** "[Customer quote]"
---
## Resources
| Resource | Purpose | Location |
|----------|---------|----------|
| [Battle card] | Competitive ammo | [Link] |
| [ROI calculator] | Value justification | [Link] |
| [Demo environment] | Live demos | [Link] |
| [Case studies] | Social proof | [Link] |
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.