Keep claims tied to verified product facts
When this instruction drafts marketing or product content, review specifications, comparisons, performance claims, and testimonials against approved evidence before publishing.
IntermediateClaude Code
Sales Enablement
Sales Enablement is an ecommerce AI skill for Claude Code, built for teams working with Codex, Claude Code, OpenClaw. Use it to find, filter, or rank the right…
- Views
- 0
- Installs
- 0
- Favorites
- 0
What this Skill does
You see shoppers struggle to find, filter, or rank the right products. Validate one concrete path first: Build a pitch deck for a SaaS product demo; Create objection handling quick-reference table for sales calls. Once it holds up, focus on removing one clear search, filter, or… Start with a small test around “Build a pitch deck for a SaaS product demo”, then check whether “Create objection handling quick-reference table for sales calls” fits the way your team actually works.
No installation needed
Copy and paste into a model chat
- Expand and copy the complete original Skill.md below.
- Open a new conversation in a compatible AI model, then paste it into the chat box.
- Add verified task details, run one low-risk example, and review the result before using it in store operations.
Original Skill.md
The complete source is shown below. Copy it from the top right to use it.
You are a B2B sales enablement expert creating collateral reps actually use. Gather: value prop, sales motion, collateral needs, current state. Principles: sales trusts what sales builds (involve reps, use their language); situation-specific over generic; scannable over comprehensive; every claim tied to business outcomes. Pitch decks: 10-12 slide framework (problem→cost→shift→approach→product→proof→case study→implementation→ROI→pricing→next steps), customize by buyer type. One-pagers: problem, solution, 3 differentiators, proof point, CTA. Objection handling: exact objection, real concern, response, proof point, follow-up. Demo scripts: opening→discovery recap→walkthrough with interaction points→close. Always demo after discovery.Get started
Starter prompts for the main use cases—copy and use them directly.
01Start with one real task
Do not begin with a store-wide rollout. Pick one reversible task where Sales Enablement can help you improve product discovery, merchandising, and onsite conversion. Use this when the input boundary, owner, and one primary measure from conversion rate, revenue per visitor, add-to-cart rate, and guardrail metrics are written down.
Show prompt and variablesHide prompt and variables
Start with one real task
Do not begin with a store-wide rollout. Pick one reversible task where Sales Enablement can help you improve product discovery, merchandising, and onsite conversion. Use this when the input boundary, owner, and one primary measure from conversion rate, revenue per visitor, add-to-cart rate, and guardrail metrics are written down.
Use the Skill above to help me with this task: Start with one real task.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Do not begin with a store-wide rollout. Pick one reversible task where Sales Enablement can help you improve product discovery, merchandising, and onsite conversion.
Return a practical result and clearly flag anything that needs human review.Replace these variables
[TASK_DETAILS]- The facts, context, or source material for this task.
[CONSTRAINTS]- Replace this placeholder with your verified store-specific information.
02Prepare the input and guardrails
Collect only the traffic and funnel data, the current page or theme, product rules, and a measurable hypothesis needed for this test. Remove unrelated personal data and state which actions must never run automatically. Use this when every input has a known source, sensitive fields are minimized, and the approver knows what the trial can read or change.
Show prompt and variablesHide prompt and variables
Prepare the input and guardrails
Collect only the traffic and funnel data, the current page or theme, product rules, and a measurable hypothesis needed for this test. Remove unrelated personal data and state which actions must never run automatically. Use this when every input has a known source, sensitive fields are minimized, and the approver knows what the trial can read or change.
Use the Skill above to help me with this task: Prepare the input and guardrails.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Collect only the traffic and funnel data, the current page or theme, product rules, and a measurable hypothesis needed for this test. Remove unrelated personal data and state which actions must never run automatically.
Return a practical result and clearly flag anything that needs human review.Replace these variables
[TASK_DETAILS]- The facts, context, or source material for this task.
[CONSTRAINTS]- Replace this placeholder with your verified store-specific information.
03Inspect the source Skill, then run it
Read the source, installation method, and permission notes before adding Sales Enablement to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a conversion experiment or merchandising change that a responsible operator can inspect, and it stayed inside the approved boundary.
Show prompt and variablesHide prompt and variables
Inspect the source Skill, then run it
Read the source, installation method, and permission notes before adding Sales Enablement to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a conversion experiment or merchandising change that a responsible operator can inspect, and it stayed inside the approved boundary.
Use the Skill above to help me with this task: Inspect the source Skill, then run it.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Read the source, installation method, and permission notes before adding Sales Enablement to a separate test project. Keep commands and Skill text exactly as published.
Return a practical result and clearly flag anything that needs human review.Replace these variables
[TASK_DETAILS]- The facts, context, or source material for this task.
[CONSTRAINTS]- Replace this placeholder with your verified store-specific information.
04Review it against a baseline
Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time. Use this when conversion rate, revenue per visitor, add-to-cart rate, and guardrail metrics has a pre-test baseline, and errors and exceptions are logged separately.
Show prompt and variablesHide prompt and variables
Review it against a baseline
Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time. Use this when conversion rate, revenue per visitor, add-to-cart rate, and guardrail metrics has a pre-test baseline, and errors and exceptions are logged separately.
Use the Skill above to help me with this task: Review it against a baseline.
Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]
Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time.
Return a practical result and clearly flag anything that needs human review.Replace these variables
[TASK_DETAILS]- The facts, context, or source material for this task.
[CONSTRAINTS]- Replace this placeholder with your verified store-specific information.
Risks and operating notes
Verify commercial terms before acting
Any price, discount, cost, or margin recommendation is only as current as the values you provide. Recheck live prices, tax, shipping, and margin rules before publishing or sending an offer.
Corey Haines
Creator of Marketing Skills, an open-source collection of reusable agent skills for content, SEO, conversion, launch, and growth work.
Risk, permissions, and limitations
Review third-party permission scopes before providing store data. Never paste payment credentials, customer passwords, or unnecessary personal data into a model. Outputs must be checked by the operator responsible for the workflow.
Content checked:
No reviews yet.