guarantee-generator

Name: guarantee-generator
Author: Affitor

3installs184forks

How to install guarantee-generator?

affitor/affiliate-skills/guarantee-generator

$npx -y skills add Affitor/affiliate-skills --skill guarantee-generator

Installs into the current project.

Summary

Create YOUR personal guarantee on top of the product's guarantee for risk reversal. Triggers on: "create a guarantee", "guarantee for my affiliate", "risk reversal", "money back guarantee", "what guarantee can I offer", "reduce buyer risk", "guarantee copy", "how to guarantee", "

Files · 1

View on GitHub

SKILL.md

1	# Guarantee Generator
2
3	Create YOUR personal guarantee that sits on top of the product's built-in guarantee. Addresses the gap: "What if I buy through your link and it doesn't work for me?" Risk reversal is the most underleveraged conversion tool in affiliate marketing.
4
5	## Stage
6
7	S4: Landing — Guarantees are landing page copy. They directly impact conversion by removing the last barrier to clicking your affiliate link.
8
9	## When to Use
10
11	- User wants to increase conversion by reducing buyer perceived risk
12	- User asks "what guarantee can I offer as an affiliate?"
13	- User says "guarantee", "risk reversal", "risk-free", "money back"
14	- After running `grand-slam-offer` or `bonus-stack-builder` to complete the offer
15	- User has low conversion rates and needs to address trust/risk objections
16
17	## Input Schema
18
19	```yaml
20	product: # REQUIRED
21	name: string # Product name
22	pricing: string # Product price
23	has_free_trial: boolean # Does the product offer a free trial?
24	has_guarantee: string # Product's existing guarantee (e.g., "30-day money back")
25
26	your_bonuses: string[] # OPTIONAL — bonuses from bonus-stack-builder
27	# Default: none
28
29	your_capacity: string # OPTIONAL — "low" \| "medium" \| "high"
30	# How much personal time you can invest
31	# Default: "medium"
32
33	audience_fears: string[] # OPTIONAL — top objections/fears
34	# Default: inferred from product type
35	```
36
37	Chaining from S4 bonus-stack-builder: Use `bonus_stack.bonuses` to reference specific bonuses in guarantee.
38
39	Chaining from S4 grand-slam-offer: Use `value_equation` to target the weakest component with the guarantee.
40
41	## Workflow
42
43	### Step 1: Gather Context
44
45	1. Understand the product's existing guarantee/refund policy
46	2. Identify top 3 buyer fears for this product category
47	3. Assess user's capacity to deliver on guarantee promises
48
49	### Step 2: Design Guarantee Options
50
51	Read `shared/references/offer-frameworks.md` for guarantee types.
52
53	Create 3 guarantee options at different commitment levels:
54
55	Option A: Light Touch (low capacity)
56	- Scope: Your bonuses only
57	- Example: "If my bonuses don't help you get started faster, I'll refund their value"
58	- Risk to you: Minimal
59
60	Option B: Support Guarantee (medium capacity)
61	- Scope: Your time + bonuses
62	- Example: "If you're stuck after 30 days, I'll personally help you implement for 1 hour"
63	- Risk to you: Moderate (capped time)
64
65	Option C: Results Guarantee (high capacity)
66	- Scope: Specific outcome
67	- Example: "If you don't [specific measurable result] in [timeframe], I'll [specific action]"
68	- Risk to you: Higher (but highest conversion impact)
69
70	### Step 3: Write Guarantee Copy
71
72	For each option, produce:
73	1. Guarantee headline — bold, specific, confident
74	2. Guarantee body — exactly what you promise, the conditions, and the timeframe
75	3. Claim process — how they reach you if they want to use the guarantee
76	4. Fine print — fair conditions (must actually use the product, specific timeframe)
77
78	### Step 4: Recommend Best Fit
79
80	Based on `your_capacity` and product type, recommend one guarantee with reasoning.
81
82	### Step 5: Self-Validation
83
84	- [ ] Guarantee is specific (not vague "satisfaction guaranteed")
85	- [ ] Guarantee is scoped to what YOU can deliver (not the product's features)
86	- [ ] Guarantee has a clear timeframe
87	- [ ] Claim process is simple and accessible
88	- [ ] Guarantee is realistic — you can actually fulfill it
89	- [ ] No guarantees about income or specific financial results (FTC)
90
91	## Output Schema
92
93	```yaml
94	output_schema_version: "1.0.0"
95	guarantee:
96	product_name: string
97	recommended_option: string # "A" \| "B" \| "C"
98	options:
99	- level: string # "light" \| "support" \| "results"
100	headline: string
101	body: string
102	claim_process: string
103	timeframe: string
104	risk_to_you: string # "minimal" \| "moderate" \| "higher"
105	conversion_impact: string # "moderate" \| "high" \| "very high"
106
107	chain_metadata:
108	skill_slug: "guarantee-generator"
109	stage: "landing"
110	timestamp: string
111	suggested_next:
112	- "landing-page-creator"
113	- "email-drip-sequence"
114	```
115
116	## Output Format
117
118	`

People who liked this also viewed

6 picks

Type

guarantee-generator

3installs184forks

View on GitHub

How to install guarantee-generator?

affitor/affiliate-skills/guarantee-generator

$npx -y skills add Affitor/affiliate-skills --skill guarantee-generator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Guarantee Generator
2
3	Create YOUR personal guarantee that sits on top of the product's built-in guarantee. Addresses the gap: "What if I buy through your link and it doesn't work for me?" Risk reversal is the most underleveraged conversion tool in affiliate marketing.
4
5	## Stage
6
7	S4: Landing — Guarantees are landing page copy. They directly impact conversion by removing the last barrier to clicking your affiliate link.
8
9	## When to Use
10
11	- User wants to increase conversion by reducing buyer perceived risk
12	- User asks "what guarantee can I offer as an affiliate?"
13	- User says "guarantee", "risk reversal", "risk-free", "money back"
14	- After running `grand-slam-offer` or `bonus-stack-builder` to complete the offer
15	- User has low conversion rates and needs to address trust/risk objections
16
17	## Input Schema
18
19	```yaml
20	product: # REQUIRED
21	name: string # Product name
22	pricing: string # Product price
23	has_free_trial: boolean # Does the product offer a free trial?
24	has_guarantee: string # Product's existing guarantee (e.g., "30-day money back")
25
26	your_bonuses: string[] # OPTIONAL — bonuses from bonus-stack-builder
27	# Default: none
28
29	your_capacity: string # OPTIONAL — "low" \| "medium" \| "high"
30	# How much personal time you can invest
31	# Default: "medium"
32
33	audience_fears: string[] # OPTIONAL — top objections/fears
34	# Default: inferred from product type
35	```
36
37	Chaining from S4 bonus-stack-builder: Use `bonus_stack.bonuses` to reference specific bonuses in guarantee.
38
39	Chaining from S4 grand-slam-offer: Use `value_equation` to target the weakest component with the guarantee.
40
41	## Workflow
42
43	### Step 1: Gather Context
44
45	1. Understand the product's existing guarantee/refund policy
46	2. Identify top 3 buyer fears for this product category
47	3. Assess user's capacity to deliver on guarantee promises
48
49	### Step 2: Design Guarantee Options
50
51	Read `shared/references/offer-frameworks.md` for guarantee types.
52
53	Create 3 guarantee options at different commitment levels:
54
55	Option A: Light Touch (low capacity)
56	- Scope: Your bonuses only
57	- Example: "If my bonuses don't help you get started faster, I'll refund their value"
58	- Risk to you: Minimal
59
60	Option B: Support Guarantee (medium capacity)
61	- Scope: Your time + bonuses
62	- Example: "If you're stuck after 30 days, I'll personally help you implement for 1 hour"
63	- Risk to you: Moderate (capped time)
64
65	Option C: Results Guarantee (high capacity)
66	- Scope: Specific outcome
67	- Example: "If you don't [specific measurable result] in [timeframe], I'll [specific action]"
68	- Risk to you: Higher (but highest conversion impact)
69
70	### Step 3: Write Guarantee Copy
71
72	For each option, produce:
73	1. Guarantee headline — bold, specific, confident
74	2. Guarantee body — exactly what you promise, the conditions, and the timeframe
75	3. Claim process — how they reach you if they want to use the guarantee
76	4. Fine print — fair conditions (must actually use the product, specific timeframe)
77
78	### Step 4: Recommend Best Fit
79
80	Based on `your_capacity` and product type, recommend one guarantee with reasoning.
81
82	### Step 5: Self-Validation
83
84	- [ ] Guarantee is specific (not vague "satisfaction guaranteed")
85	- [ ] Guarantee is scoped to what YOU can deliver (not the product's features)
86	- [ ] Guarantee has a clear timeframe
87	- [ ] Claim process is simple and accessible
88	- [ ] Guarantee is realistic — you can actually fulfill it
89	- [ ] No guarantees about income or specific financial results (FTC)
90
91	## Output Schema
92
93	```yaml
94	output_schema_version: "1.0.0"
95	guarantee:
96	product_name: string
97	recommended_option: string # "A" \| "B" \| "C"
98	options:
99	- level: string # "light" \| "support" \| "results"
100	headline: string
101	body: string
102	claim_process: string
103	timeframe: string
104	risk_to_you: string # "minimal" \| "moderate" \| "higher"
105	conversion_impact: string # "moderate" \| "high" \| "very high"
106
107	chain_metadata:
108	skill_slug: "guarantee-generator"
109	stage: "landing"
110	timestamp: string
111	suggested_next:
112	- "landing-page-creator"
113	- "email-drip-sequence"
114	```
115
116	## Output Format
117
118	`

People who liked this also viewed

6 picks

Type