Sales Enablement V2

Sales Enablement

Overview

This public intake copy packages plugins/antigravity-awesome-skills/skills/sales-enablement from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Sales Enablement 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.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Before Starting, Sales Deck / Pitch Deck, One-Pagers / Leave-Behinds, Objection Handling Docs, ROI Calculators & Value Props, Demo Scripts & Talk Tracks.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Use when building decks, one-pagers, objection handling docs, or demo scripts.
• Use when a sales team needs collateral tailored to stage, persona, or use case.
• Use when the asset should help reps close deals rather than drive top-of-funnel traffic.
• Use when the request clearly matches the imported source intent: Create sales collateral such as decks, one-pagers, objection docs, demo scripts, playbooks, and proposal templates. Use when a sales team needs assets that help reps move deals forward and close.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
2. Read the overview and provenance files before loading any copied upstream support files.
3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
5. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Before Starting

Check for product marketing context first: If .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.

Gather this context (ask if not provided):

1. Value Proposition & Differentiators

   • What do you sell and who is it for?
   • What makes you different from the next best alternative?
   • What outcomes can you prove?

2. Sales Motion

   • How do you sell? (self-serve, inside sales, field sales, hybrid)
   • Average deal size and sales cycle length
   • Key personas involved in the buying decision

3. Collateral Needs

   • What specific assets do you need?
   • What stage of the funnel are they for?
   • Who will use them? (AE, SDR, champion, prospect)

4. Current State

   • What materials exist today?
   • What's working and what's not?
   • What do reps ask for most?

Examples

Example 1: Ask for the upstream workflow directly

Use @sales-enablement-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @sales-enablement-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @sales-enablement-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @sales-enablement-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Sales Uses What Sales Trusts 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.

• Situation-Specific, Not Generic 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.

Imported Operating Notes

Imported: Core Principles

Sales Uses What Sales Trusts

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.

Situation-Specific, Not Generic

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.

Scannable Over Comprehensive

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.

Tie Back to Business Outcomes

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%."

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/sales-enablement, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

• deck-frameworks.md
• demo-scripts.md
• objection-library.md
• one-pager-templates.md
• evals.json
• deck-frameworks.md

Imported Reference Notes

Imported: Sales Deck / Pitch Deck

10-12 Slide Framework

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

Deck Principles

• Story arc, not feature tour. Every deck tells a story: the world has a problem, there's a better way, here's proof, here's how to get there.
• One idea per slide. If you need two points, use two slides.
• Design for presenting, not reading. Slides support the conversation — they don't replace it. Minimal text, strong visuals.

Customization by Buyer Type

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

Imported: One-Pagers / Leave-Behinds

When to Use

• Post-meeting recap — Reinforce what you discussed, keep momentum
• Champion internal selling — Arm your champion to sell for you
• Trade show handout — Quick intro that drives follow-up

Structure

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

Design Principles

• One page, literally. Front only, or front and back maximum.
• Scannable in 30 seconds. Bold headers, short bullets, whitespace.
• Include your logo, website, and a specific contact (not info@).
• Match your brand but keep it clean — this is a sales tool, not a brand piece.

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

Imported: Objection Handling Docs

Objection Categories

Response Framework

For each objection, document:

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

Two Formats

• Quick-reference table for live calls — objection, one-line response, proof point. Fits on one screen.
• Detailed doc for prep and training — full context, talk tracks, role-play scenarios.

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

Imported: ROI Calculators & Value Props

Calculator Design

Inputs (current state metrics the prospect provides):

• Time spent on manual processes
• Current tool costs
• Error rates or inefficiency metrics
• Team size

Calculations (your formula for value):

• Time saved per week/month/year
• Cost reduction (tools, headcount, errors)
• Revenue impact (faster deals, higher conversion)

Outputs (what the prospect sees):

• Annual ROI percentage
• Payback period in months
• Total 3-year value

Value Prop by Persona

Implementation Options

• Spreadsheet — Fastest to build, easy to customize per deal. Works for inside sales.
• Web tool — More polished, captures leads, scales better. Worth building if deal volume is high.
• Slide-based — ROI story embedded in the deck. Good for executive presentations.

Imported: Demo Scripts & Talk Tracks

Script Structure

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

Talk Track Types

Key Principles

• Demo after discovery, not before. If you don't know their pain, you're guessing which features matter.
• Customize to their use case. Use their terminology, their data (if possible), their workflow.
• Leave time for questions. A demo where the prospect doesn't talk is a demo that doesn't close.

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

Imported: Case Study Briefs (Sales Format)

How Sales Case Studies Differ

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

Structure

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

Organization

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

• By industry — "Show me a case study for healthcare"
• By use case — "Show me someone who used us for X"
• By company size — "Show me an enterprise example"

Imported: Proposal Templates

Structure

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

Customization Guidance

• Mirror their language from discovery calls
• Reference specific pain points they mentioned
• Include only relevant case studies (same industry or use case)
• Name the stakeholders you've spoken with

Common Mistakes

• Too long — If it's over 10 pages, it won't get read. Aim for 5-7.
• Too generic — Templated proposals signal low effort. Customize the exec summary at minimum.
• Burying the price — Don't make them hunt for it. Be transparent and confident.

Imported: Sales Playbooks

What Goes in a Playbook

• Buyer profile — Who you're selling to, their goals and pains
• Qualification criteria — BANT, MEDDIC, or your framework
• Discovery questions — Organized by topic, not a script
• Objection handling — Top 10 objections with responses
• Competitive positioning — How you win against each competitor
• Demo flow — Recommended sequence for each persona
• Email templates — Follow-up, proposal, check-in, breakup

When to Build

• New product launch — Reps need a single source of truth
• New market segment — Different buyers need different approaches
• New hire ramp — Playbooks cut ramp time significantly

Keeping It Living

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.

Imported: Buyer Persona Cards

Card Structure

Persona Types

• Economic buyer — Signs the check. Cares about ROI and risk.
• Technical buyer — Evaluates the product. Cares about capabilities and integration.
• End user — Uses it daily. Cares about ease and workflow fit.
• Champion — Advocates internally. Needs ammunition to sell for you.
• Blocker — Opposes the purchase. Understand their concern to neutralize it.

Imported: Output Format

Deliver the right format for each asset type:

Imported: Task-Specific Questions

If context is missing, ask:

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

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.