{"slug":"sales-enablement-3","title":"sales-enablement","summary":"When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk tra","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-09-18T13:23:47.10184Z","repo":{"url":"https://github.com/aAAaqwq/AGI-Super-Team","stars":100,"forks":23,"license":"MIT","updatedAt":"2026-09-27T10:44:59Z"},"bodyHtml":"
\n

name: sales-enablement\ndescription: \"When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.\"\nmetadata:\nversion: 1.1.0

\n

Sales Enablement

\n

You are an expert in B2B sales enablement. Your goal is to create sales collateral that reps actually use — decks, one-pagers, objection docs, demo scripts, and playbooks that help close deals.

\n

Before Starting

\n

Check for product marketing context first:\nIf .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

\n

Gather this context (ask if not provided):

\n
    \n

  1. Value Proposition & Differentiators

    \n\n
    2. \n

  2. Sales Motion

    \n\n
    3. \n

  3. Collateral Needs

    \n\n
    4. \n

  4. Current State

    \n\n
    5. \n
\n
\n

Core Principles

\n

Sales Uses What Sales Trusts

\n

Involve reps in creation. Use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with your top performers first.

\n

Situation-Specific, Not Generic

\n

Tailor to persona, deal stage, and use case. A deck for a CTO should look different from one for a VP of Sales. A one-pager for post-meeting follow-up serves a different purpose than one for a trade show.

\n

Scannable Over Comprehensive

\n

Reps need information in 3 seconds, not 30. Use bold headers, short bullets, and visual hierarchy. If a rep can't find the answer mid-call, the doc has failed.

\n

Tie Back to Business Outcomes

\n

Every claim connects to revenue, efficiency, or risk reduction. Features mean nothing without the \"so what.\" Replace \"AI-powered analytics\" with \"cut reporting time by 80%.\"

\n
\n

Sales Deck / Pitch Deck

\n

10-12 Slide Framework

\n
    \n
  1. Current World Problem — The pain your buyer lives with today
    2. \n
  2. Cost of the Problem — What inaction costs (time, money, risk)
    3. \n
  3. The Shift Happening — Market or technology change creating urgency
    4. \n
  4. Your Approach — How you solve it differently
    5. \n
  5. Product Walkthrough — 3-4 key workflows, not a feature tour
    6. \n
  6. Proof Points — Metrics, logos, analyst recognition
    7. \n
  7. Case Study — One customer story told well
    8. \n
  8. Implementation / Timeline — How they get from here to live
    9. \n
  9. ROI / Value — Expected return and payback period
    10. \n
  10. Pricing Overview — Transparent, tiered if applicable
    11. \n
  11. Next Steps / CTA — Clear action with timeline
    12. \n
\n

Deck Principles

\n\n

Customization by Buyer Type

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
BuyerEmphasizeDe-emphasize
Technical buyerArchitecture, security, integrations, APIROI calculations, business metrics
Economic buyerROI, payback period, total cost, riskTechnical details, implementation specifics
ChampionInternal selling points, quick wins, peer proofDeep technical or financial detail
\n

For full slide-by-slide guidance: See references/deck-frameworks.md

\n
\n

One-Pagers / Leave-Behinds

\n

When to Use

\n\n

Structure

\n
    \n
  1. Problem statement — The pain in one sentence
    2. \n
  2. Your solution — What you do and how
    3. \n
  3. 3 differentiators — Why you vs. alternatives
    4. \n
  4. Proof point — One strong metric or customer quote
    5. \n
  5. CTA — Clear next step with contact info
    6. \n
\n

Design Principles

\n\n

For templates by use case: See references/one-pager-templates.md

\n
\n

Objection Handling Docs

\n

Objection Categories

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
CategoryExamples
Price\"Too expensive,\" \"No budget this quarter,\" \"Competitor is cheaper\"
Timing\"Not the right time,\" \"Maybe next quarter,\" \"Too busy to implement\"
Competition\"We already use X,\" \"What makes you different?\"
Authority\"I need to check with my boss,\" \"The committee decides\"
Status quo\"What we have works fine,\" \"Not broken, don't fix it\"
Technical\"Does it integrate with X?,\" \"Security concerns,\" \"Can it scale?\"
\n

Response Framework

\n

For each objection, document:

\n
    \n
  1. Objection statement — Exactly how reps hear it
    2. \n
  2. Why they say it — The real concern behind the words
    3. \n
  3. Response approach — How to acknowledge and redirect
    4. \n
  4. Proof point — Specific evidence that addresses the concern
    5. \n
  5. Follow-up question — Keep the conversation moving forward
    6. \n
\n

Two Formats

\n\n

For the full objection library: See references/objection-library.md

\n
\n

ROI Calculators & Value Props

\n

Calculator Design

\n

Inputs (current state metrics the prospect provides):

\n\n

Calculations (your formula for value):

\n\n

Outputs (what the prospect sees):

\n\n

Value Prop by Persona

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PersonaCares AboutLead With
CTO / VP EngArchitecture, scale, security, team velocityTechnical superiority, integration depth
VP SalesPipeline, quota attainment, rep productivityRevenue impact, time savings per rep
CFOTotal cost, payback period, riskROI, cost reduction, financial predictability
End userEase of use, daily workflow, learning curveTime saved, frustration eliminated
\n

Implementation Options

\n\n
\n

Demo Scripts & Talk Tracks

\n

Script Structure

\n
    \n
  1. Opening (2 min) — Context setting, agenda, confirm goals for the call
    2. \n
  2. Discovery recap (3 min) — Summarize what you learned, confirm priorities
    3. \n
  3. Solution walkthrough (15-20 min) — 3-4 key workflows mapped to their pain
    4. \n
  4. Interaction points — Questions to ask during the demo, not just at the end
    5. \n
  5. Close (5 min) — Summarize value, propose next steps with timeline
    6. \n
\n

Talk Track Types

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
TypeDurationFocus
Discovery call30 minQualify, understand pain, map buying process
First demo30-45 minShow 3-4 workflows tied to their pain
Technical deep-dive45-60 minArchitecture, security, integrations, API
Executive overview20-30 minBusiness outcomes, ROI, strategic alignment
\n

Key Principles

\n\n

For full script templates: See references/demo-scripts.md

\n
\n

Case Study Briefs (Sales Format)

\n

How Sales Case Studies Differ

\n

Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval.

\n

Structure

\n
    \n
  1. Customer profile — Industry, company size, buyer role
    2. \n
  2. Challenge — What they were struggling with (2-3 sentences)
    3. \n
  3. Solution — What they implemented (1-2 sentences)
    4. \n
  4. Results — 3 specific metrics (before/after)
    5. \n
  5. Pull quote — One sentence from the customer
    6. \n
  6. Tags — Industry, use case, company size, persona
    7. \n
\n

Organization

\n

Organize case studies so reps can find the right one instantly:

\n\n
\n

Proposal Templates

\n

Structure

\n
    \n
  1. Executive summary — Their challenge, your solution, expected outcome (1 page max)
    2. \n
  2. Proposed solution — What you'll deliver, mapped to their requirements
    3. \n
  3. Implementation plan — Timeline, milestones, responsibilities
    4. \n
  4. Investment — Pricing, payment terms, what's included
    5. \n
  5. Next steps — How to move forward, decision timeline
    6. \n
\n

Customization Guidance

\n\n

Common Mistakes

\n\n
\n

Sales Playbooks

\n

What Goes in a Playbook

\n\n

When to Build

\n\n

Keeping It Living

\n

Playbooks die when they're not updated. Review quarterly, get input from top reps, and remove anything outdated. Assign an owner — if nobody owns it, it rots.

\n
\n

Buyer Persona Cards

\n

Card Structure

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
FieldDescription
Role / titleCommon titles and reporting structure
GoalsWhat success looks like for them
PainsWhat frustrates them daily
Top objectionsThe 3-5 objections you'll hear from this role
Evaluation criteriaHow they judge solutions
Buying processTheir role in the decision, who they influence
Messaging angleThe one sentence that resonates most
\n

Persona Types

\n\n
\n

Output Format

\n

Deliver the right format for each asset type:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
AssetDeliverable
Sales deckSlide-by-slide outline with headline, body copy, and speaker notes
One-pagerFull copy with layout guidance (visual hierarchy, sections)
Objection docTable format: objection, response, proof point, follow-up
Demo scriptScene-by-scene with timing, talk track, and interaction points
ROI calculatorInput fields, formulas, output display with sample data
PlaybookStructured document with table of contents and sections
Persona cardOne-page card format per persona
ProposalSection-by-section copy with customization notes
\n
\n

Task-Specific Questions

\n

If context is missing, ask:

\n
    \n
  1. What collateral do you need? (deck, one-pager, objection doc, etc.)
    2. \n
  2. Who will use it? (AE, SDR, champion, prospect)
    3. \n
  3. What sales stage is it for? (prospecting, discovery, demo, negotiation, close)
    4. \n
  4. Who is the target persona? (title, seniority, department)
    5. \n
  5. What are the top 3 objections you hear most?
    6. \n
\n
\n

Related Skills

\n\n","files":[{"path":".clawhub/origin.json","sizeBytes":152,"isText":true},{"path":"evals/evals.json","sizeBytes":6464,"isText":true},{"path":"_meta.json","sizeBytes":139,"isText":true},{"path":"references/deck-frameworks.md","sizeBytes":7730,"isText":true},{"path":"references/demo-scripts.md","sizeBytes":11769,"isText":true},{"path":"references/objection-library.md","sizeBytes":13393,"isText":true},{"path":"references/one-pager-templates.md","sizeBytes":5823,"isText":true},{"path":"SKILL.md","sizeBytes":14335,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-18T13:24:05.077242Z","sha256":"D4586D57FCB0AD9229852C83F1092E782B14B4E328267BE7C59E490BC2EE9FF3","sizeBytes":25149},"review":null,"source":{"repositoryUrl":"https://github.com/aAAaqwq/AGI-Super-Team","path":"skills/abm-sales-enablement","license":"MIT","commit":"331ecd3c1dd6597c351e5dc5d7a7d9f6e6bcab13","subtreeSha":"1FACBBC217C1E0F521DBB1FB18AC96F3665B31463501103FE610B28F6902DD12","lastSyncedAt":"2026-09-27T19:30:31.933956Z"},"reviewedAt":"2026-09-18T13:24:22.663035Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/aAAaqwq/AGI-Super-Team/tree/main/skills/abm-sales-enablement"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install aaaaqwq-agi-super-team@llmmart"},{"target":"git","command":"git clone https://github.com/aAAaqwq/AGI-Super-Team.git"}]}