Stats
Actions
Tags
From sales-enablement
Create enablement materials for channel partners, co-sell partners, and technology partners — partner playbooks, co-sell guides, joint value propositions, and partner onboarding kits. Use this skill when building partner sales materials, co-selling strategies, channel partner programs, joint go-to-market motions, or when someone says "enable our partners", "partner playbook", "co-sell guide", "channel partner kit", or "help partners sell our product". Also trigger when someone mentions partner ecosystem, alliance management, channel strategy, or co-marketing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sales-enablement:partner-enablementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help channel, co-sell, and technology partners sell your product effectively. Partners are an extension of your sales team — but they have less context, less training, and less urgency. The materials need to be simpler, more self-serve, and more opinionated than internal enablement.
Help channel, co-sell, and technology partners sell your product effectively. Partners are an extension of your sales team — but they have less context, less training, and less urgency. The materials need to be simpler, more self-serve, and more opinionated than internal enablement.
Each type needs different enablement — a reseller needs a full playbook; a referral partner needs a one-pager.
┌─────────────────────────────────────────────────────────────────┐
│ PARTNER ENABLEMENT │
├─────────────────────────────────────────────────────────────────┤
│ DELIVERABLES │
│ 1. Partner Playbook — Complete selling guide for partners │
│ 2. Co-Sell Guide — How to run joint opportunities │
│ 3. Joint Value Prop — Combined messaging for the partnership │
│ 4. Partner Onboarding Kit — Everything a new partner needs │
│ 5. Deal Registration Guide — How to register and track deals │
│ 6. Partner Battle Card — Competitive positioning for partners │
├─────────────────────────────────────────────────────────────────┤
│ KEY PRINCIPLE │
│ Partner materials must be simpler than internal materials. │
│ Partners have less time, less context, and more products to │
│ sell. Make it dead simple to understand, position, and sell. │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + ~~CRM: Partner-sourced deal data and win rates │
│ + ~~CRM: Partner deal pipeline and conversion metrics │
│ + ~~CRM: Customer profiles for partner success stories │
│ + ~~data enrichment (ZoomInfo): Partner company research │
│ + ~~data enrichment (ZoomInfo): Partner customer tech stacks │
│ + ~~data enrichment (Clay): Partner company enrichment │
│ + ~~data enrichment (LinkedIn): Partner contact profiles │
│ + ~~data enrichment (LinkedIn): Partner company updates │
│ + ~~conversation intelligence (Gong): Partner call patterns │
│ + ~~conversation intelligence (Gong): Joint call recordings │
│ + ~~chat: Partner feedback and deal discussions │
└─────────────────────────────────────────────────────────────────┘
CRITICAL: Before asking for partner context, pull data from connected tools. Partner materials are strongest when grounded in real deal data from the partner channel.
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:
deals for deals associated with the partner (by partner name, source, or deal type).
dealname, amount, dealstage, closedate, createdate, pipeline, hubspot_owner_id, dealtype, description, closed_won_reason, closed_lost_reasonname, industry, numberofemployees, annualrevenuefirstname, lastname, jobtitle, emailZoomInfo (if available):
zoominfo_search_company with the partner's company name.
zoominfo_get_tech_stack on partner's existing customer base.
Clay (if available):
clay_enrich_company with the partner domain.
LinkedIn (if available):
linkedin_get_profile for partner sales leadership.
linkedin_search_companies for partner company.
Check if you have access to Gong tools (look for tools prefixed with gong_).
If Gong tools ARE available:
gong_search_calls with the partner company name.
gong_get_call_stats on partner-involved calls.
gong_get_transcript on partner-led calls.
If chat tools are available (slack_search_public, slack_search_public_and_private):
"I pulled data for the [Partner] channel: [N] partner-sourced deals in the last [period] — [X]% win rate with $[X] avg deal size. Per CRM, partners win most with [company profile] companies, and common loss reasons include [reasons]. [If Gong:] Found [N] joint calls — partners tend to [positioning pattern]. [If ZoomInfo:] Partner focuses on [market/industry] with [N] customers. Building partner materials now..."
After the auto-pull, ask ONLY for what the tools couldn't provide:
Build using ALL evidence. Use partner-channel deal data as primary evidence. Cite sources: "Per CRM (partner deals):", "Per Gong (joint calls):", "Per ZoomInfo:", "Per Slack:". Keep materials simpler than internal equivalents — partners have less time and context.
memory/deal-patterns.md with partner channel patterns discoveredmemory/content-registry.md with new partner enablement assetsmemory/changelog.md# Partner Sales Playbook: [Your Product]
**For:** [Partner Type] Partners
**Version:** [X.0]
**Last Updated:** [Date]
---
## Your 60-Second Pitch
[The simplest possible explanation of what the product does, who it's for, and why they should care. If a partner can't explain this in a meeting without preparation, the pitch is too complex.]
---
## Who To Sell This To
### Ideal Customer
| Attribute | Detail |
|-----------|--------|
| Company size | [Range] |
| Industry | [Top 3] |
| Trigger event | [What makes them ready to buy now] |
### Best-Fit Personas
**Primary:** [Title] — [What they care about in one sentence]
**Secondary:** [Title] — [What they care about]
### Qualifying Questions
Ask these three questions. If the prospect answers "yes" to two or more, they're a fit:
1. "[Simple qualifying question]"
2. "[Question]"
3. "[Question]"
---
## How to Position
### Lead with this:
> "[One sentence value proposition that works in any conversation]"
### Avoid saying:
- [Common mistake partners make when positioning]
- [Technical detail that confuses prospects at this stage]
### Customer Proof Point
"[Customer X] deployed [your product] and saw [specific result] in [timeframe]."
---
## Pricing & Deal Structure
| Tier/SKU | Price | Partner Margin | Notes |
|----------|-------|---------------|-------|
| [Tier] | $[X] | [X]% | [When to recommend] |
---
## Common Objections (Top 3)
### "[Objection 1]"
> "[Simple response — one paragraph max]"
### "[Objection 2]"
> "[Response]"
### "[Objection 3]"
> "[Response]"
---
## Deal Registration & Support
**How to register:** [Simple steps]
**Support contact:** [Who to reach out to]
**Demo support:** [How to get a demo for their prospect]
**SLA:** [Response time for partner requests]
---
## Resources
| Resource | What It Is | Link |
|----------|-----------|------|
| Demo video | [Description] | [Link] |
| One-pager | [Description] | [Link] |
| Case study | [Description] | [Link] |
npx claudepluginhub jbalbu01/sales-enablement-pluginCreate 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 B2B sales collateral: pitch decks, one-pagers, objection docs, demo scripts, and playbooks. Includes a 10-12 slide framework and checks for existing product-marketing context.
Creates sales collateral including pitch decks, one-pagers, objection handling docs, and demo scripts for B2B sales teams.