sales-enablement

Name: sales-enablement
Author: davidpc007

140stars1.3kforks

How to install sales-enablement?

davidpc007/openclaw-marketing-skills/sales-enablement

$npx -y skills add davidpc007/openclaw-marketing-skills --skill sales-enablement

Installs into the current project.

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

Files · 1

View on GitHub

SKILL.md

1	# Sales Enablement
2
3	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.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing-context.md` exists (or `.agents/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.
9
10	Gather this context (ask if not provided):
11
12	1. Value Proposition & Differentiators
13	- What do you sell and who is it for?
14	- What makes you different from the next best alternative?
15	- What outcomes can you prove?
16
17	2. Sales Motion
18	- How do you sell? (self-serve, inside sales, field sales, hybrid)
19	- Average deal size and sales cycle length
20	- Key personas involved in the buying decision
21
22	3. Collateral Needs
23	- What specific assets do you need?
24	- What stage of the funnel are they for?
25	- Who will use them? (AE, SDR, champion, prospect)
26
27	4. Current State
28	- What materials exist today?
29	- What's working and what's not?
30	- What do reps ask for most?
31
32	---
33
34	## Core Principles
35
36	### Sales Uses What Sales Trusts
37	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.
38
39	### Situation-Specific, Not Generic
40	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.
41
42	### Scannable Over Comprehensive
43	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.
44
45	### Tie Back to Business Outcomes
46	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%."
47
48	---
49
50	## Sales Deck / Pitch Deck
51
52	### 10-12 Slide Framework
53
54	1. Current World Problem — The pain your buyer lives with today
55	2. Cost of the Problem — What inaction costs (time, money, risk)
56	3. The Shift Happening — Market or technology change creating urgency
57	4. Your Approach — How you solve it differently
58	5. Product Walkthrough — 3-4 key workflows, not a feature tour
59	6. Proof Points — Metrics, logos, analyst recognition
60	7. Case Study — One customer story told well
61	8. Implementation / Timeline — How they get from here to live
62	9. ROI / Value — Expected return and payback period
63	10. Pricing Overview — Transparent, tiered if applicable
64	11. Next Steps / CTA — Clear action with timeline
65
66	### Deck Principles
67
68	- 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.
69	- One idea per slide. If you need two points, use two slides.
70	- Design for presenting, not reading. Slides support the conversation — they don't replace it. Minimal text, strong visuals.
71
72	### Customization by Buyer Type
73
74	\| Buyer \| Emphasize \| De-emphasize \|
75	\|-------\|-----------\|--------------\|
76	\| Technical buyer \| Architecture, security, integrations, API \| ROI calculations, business metrics \|
77	\| Economic buyer \| ROI, payback period, total cost, risk \| Technical details, implementation specifics \|
78	\| Champion \| Internal selling points, quick wins, peer proof \| Deep technical or financial detail \|
79
80	For full slide-by-slide guidance: See [references/deck-frameworks.md](references/deck-frameworks.md)
81
82	---
83
84	## One-Pagers / Leave-Behinds
85
86	### When to Use
87
88	- Post-meeting recap — Reinforce what you discussed, keep momentum
89	- Champion internal selling — Arm your champion to sell for you
90	- Trade show handout — Quick intro that drives follow-up
91
92	### Structure
93
94	1. Problem statement — The pain in one sentence
95	2. Your solution — What you do and how
96	3. 3 differentiators — Why you vs. alternatives
97	4. Proof point — One strong metric or customer quote
98	5. CTA — Clear next step with contact info
99
100	### Design Principles
101
102	- One page, literally. Front

People who liked this also viewed

6 picks

Type

sales-enablement

140stars1.3kforks

View on GitHub

How to install sales-enablement?

davidpc007/openclaw-marketing-skills/sales-enablement

$npx -y skills add davidpc007/openclaw-marketing-skills --skill sales-enablement

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Sales Enablement
2
3	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.
4
5	## Before Starting
6
7	Check for product marketing context first:
8	If `.agents/product-marketing-context.md` exists (or `.agents/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.
9
10	Gather this context (ask if not provided):
11
12	1. Value Proposition & Differentiators
13	- What do you sell and who is it for?
14	- What makes you different from the next best alternative?
15	- What outcomes can you prove?
16
17	2. Sales Motion
18	- How do you sell? (self-serve, inside sales, field sales, hybrid)
19	- Average deal size and sales cycle length
20	- Key personas involved in the buying decision
21
22	3. Collateral Needs
23	- What specific assets do you need?
24	- What stage of the funnel are they for?
25	- Who will use them? (AE, SDR, champion, prospect)
26
27	4. Current State
28	- What materials exist today?
29	- What's working and what's not?
30	- What do reps ask for most?
31
32	---
33
34	## Core Principles
35
36	### Sales Uses What Sales Trusts
37	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.
38
39	### Situation-Specific, Not Generic
40	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.
41
42	### Scannable Over Comprehensive
43	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.
44
45	### Tie Back to Business Outcomes
46	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%."
47
48	---
49
50	## Sales Deck / Pitch Deck
51
52	### 10-12 Slide Framework
53
54	1. Current World Problem — The pain your buyer lives with today
55	2. Cost of the Problem — What inaction costs (time, money, risk)
56	3. The Shift Happening — Market or technology change creating urgency
57	4. Your Approach — How you solve it differently
58	5. Product Walkthrough — 3-4 key workflows, not a feature tour
59	6. Proof Points — Metrics, logos, analyst recognition
60	7. Case Study — One customer story told well
61	8. Implementation / Timeline — How they get from here to live
62	9. ROI / Value — Expected return and payback period
63	10. Pricing Overview — Transparent, tiered if applicable
64	11. Next Steps / CTA — Clear action with timeline
65
66	### Deck Principles
67
68	- 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.
69	- One idea per slide. If you need two points, use two slides.
70	- Design for presenting, not reading. Slides support the conversation — they don't replace it. Minimal text, strong visuals.
71
72	### Customization by Buyer Type
73
74	\| Buyer \| Emphasize \| De-emphasize \|
75	\|-------\|-----------\|--------------\|
76	\| Technical buyer \| Architecture, security, integrations, API \| ROI calculations, business metrics \|
77	\| Economic buyer \| ROI, payback period, total cost, risk \| Technical details, implementation specifics \|
78	\| Champion \| Internal selling points, quick wins, peer proof \| Deep technical or financial detail \|
79
80	For full slide-by-slide guidance: See [references/deck-frameworks.md](references/deck-frameworks.md)
81
82	---
83
84	## One-Pagers / Leave-Behinds
85
86	### When to Use
87
88	- Post-meeting recap — Reinforce what you discussed, keep momentum
89	- Champion internal selling — Arm your champion to sell for you
90	- Trade show handout — Quick intro that drives follow-up
91
92	### Structure
93
94	1. Problem statement — The pain in one sentence
95	2. Your solution — What you do and how
96	3. 3 differentiators — Why you vs. alternatives
97	4. Proof point — One strong metric or customer quote
98	5. CTA — Clear next step with contact info
99
100	### Design Principles
101
102	- One page, literally. Front

People who liked this also viewed

6 picks

Type