Sales Enablement workflow skill. Use this skill when the user needs 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 and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills-claude/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 EXTERNAL_SOURCE.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.
関連 Skill
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
Situation
Start here
Why it matters
First-time use
EXTERNAL_SOURCE.json
Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
references/deck-frameworks.md
Starts with the smallest copied file that materially changes execution
Supporting context
references/demo-scripts.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
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.
Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
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):
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?
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
Collateral Needs
What specific assets do you need?
What stage of the funnel are they for?
Who will use them? (AE, SDR, champion, prospect)
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 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 against EXTERNAL_SOURCE.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 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 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-claude/skills/sales-enablement, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open EXTERNAL_SOURCE.json, ORIGIN.md, and the most relevant copied upstream files. Load only the files that materially change the answer, 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-v2 - 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.
@20-andruia-niche-intelligence-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@2d-games - 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.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/deck-frameworks.md
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
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
Field
Description
Role / title
Common titles and reporting structure
Goals
What success looks like for them
Pains
What frustrates them daily
Top objections
The 3-5 objections you'll hear from this role
Evaluation criteria
How they judge solutions
Buying process
Their role in the decision, who they influence
Messaging angle
The one sentence that resonates most
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:
Asset
Deliverable
Sales deck
Slide-by-slide outline with headline, body copy, and speaker notes
One-pager
Full copy with layout guidance (visual hierarchy, sections)
Objection doc
Table format: objection, response, proof point, follow-up
Demo script
Scene-by-scene with timing, talk track, and interaction points
ROI calculator
Input fields, formulas, output display with sample data
Playbook
Structured document with table of contents and sections
Persona card
One-page card format per persona
Proposal
Section-by-section copy with customization notes
Imported: Task-Specific Questions
If context is missing, ask:
What collateral do you need? (deck, one-pager, objection doc, etc.)
Who will use it? (AE, SDR, champion, prospect)
What sales stage is it for? (prospecting, discovery, demo, negotiation, close)
Who is the target persona? (title, seniority, department)
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.
02
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.