bonus-stack-builder

Name: bonus-stack-builder
Author: Affitor

4installs184forks

How to install bonus-stack-builder?

affitor/affiliate-skills/bonus-stack-builder

$npx -y skills add Affitor/affiliate-skills --skill bonus-stack-builder

Installs into the current project.

Summary

Design exclusive bonus packages that make YOUR affiliate link the obvious choice. Triggers on: "create bonuses for", "bonus stack", "what bonuses should I offer", "bonus ideas for", "exclusive bonuses", "differentiate my affiliate link", "why buy through my link", "affiliate bonu

Files · 1

View on GitHub

SKILL.md

1	# Bonus Stack Builder
2
3	Design exclusive bonus packages that make YOUR affiliate link the only rational choice. The product is the same through every affiliate's link — your bonuses are what differentiate you. Creates specific, deliverable bonuses matched to your skills and audience needs.
4
5	## Stage
6
7	S4: Landing — Bonuses live on the landing page. They are the conversion differentiator between your link and every other affiliate promoting the same product.
8
9	## When to Use
10
11	- User promotes an affiliate product and wants to stand out from other affiliates
12	- User asks "why would someone buy through MY link?"
13	- User wants to increase conversion rates on existing promotions
14	- User says "bonus", "bonus stack", "exclusive offer", "differentiate"
15	- After running `grand-slam-offer` to flesh out the bonus suggestions
16
17	## Input Schema
18
19	```yaml
20	product: # REQUIRED — the affiliate product
21	name: string # Product name
22	description: string # What it does
23	pricing: string # Product price
24	url: string # Affiliate link
25	tags: string[] # e.g., ["ai", "video", "saas"]
26
27	your_skills: string[] # OPTIONAL — what you can create/offer
28	# e.g., ["writing", "design", "coding", "consulting"]
29	# Default: inferred from context
30
31	audience_pain_points: string[] # OPTIONAL — biggest struggles of your audience
32	# Default: inferred from product category
33
34	existing_bonuses: string[] # OPTIONAL — bonuses you already offer
35	# Default: none
36	```
37
38	Chaining from S4 grand-slam-offer: If `grand-slam-offer` was run, use `offer_stack.bonuses` as starting point and flesh them out.
39
40	## Workflow
41
42	### Step 1: Gather Context
43
44	1. If product data available from chain, use directly. Otherwise `web_search` for product details.
45	2. Identify the product's top 3 pain points it solves
46	3. Identify the product's top 3 gaps (things users struggle with after buying)
47	4. Research: `"[product] complaints" OR "[product] struggles" OR "[product] learning curve"` to find bonus opportunities
48
49	### Step 2: Design Bonus Stack
50
51	Read `shared/references/offer-frameworks.md` for bonus types and rules.
52
53	For each bonus, define:
54	1. What it is — specific deliverable, not vague
55	2. What problem it solves — maps to a pain point or product gap
56	3. Format — PDF, video, template, spreadsheet, community access, call
57	4. Perceived value — what you'd charge if sold separately
58	5. Effort to create — low/medium/high (helps user prioritize)
59	6. Exclusivity — why this is ONLY available through your link
60
61	Design 5-7 bonuses across these tiers:
62	- Tier 1: Quick wins (low effort to create, high perceived value) — templates, checklists, swipe files
63	- Tier 2: Deep value (medium effort, high impact) — mini-course, workshop recording, tool
64	- Tier 3: Premium (high effort, ultimate differentiator) — personal support, community, coaching
65
66	### Step 3: Calculate Stack Value
67
68	- Sum perceived values of all bonuses
69	- Compare to product price — bonus value should be 3-10x product price
70	- Identify the "hero bonus" — the one that does the most persuasive heavy lifting
71
72	### Step 4: Write Bonus Copy
73
74	For each bonus, write:
75	- Name — specific and benefit-driven (not "Bonus #1")
76	- One-liner — what it is + what it does for them
77	- Value statement — "$XX value — FREE with your purchase"
78	- Delivery method — how they get it after purchasing
79
80	### Step 5: Self-Validation
81
82	- [ ] Each bonus is specific and deliverable (not vague promises)
83	- [ ] At least one bonus addresses the product's biggest gap
84	- [ ] Total bonus value exceeds product price
85	- [ ] At least one "exclusive" bonus (only through your link)
86	- [ ] All bonuses are within your skills to actually create
87	- [ ] No income claims or unrealistic promises
88
89	## Output Schema
90
91	```yaml
92	output_schema_version: "1.0.0"
93	bonus_stack:
94	product_name: string
95	total_value: string # Total perceived value of all bonuses
96	product_price: string # For comparison
97	hero_bonus: string # The most compelling bonus name
98	bonuses:
99	- name: string
100	description: string
101	problem_solved: string
102	format: string

People who liked this also viewed

6 picks

Type

bonus-stack-builder

4installs184forks

View on GitHub

How to install bonus-stack-builder?

affitor/affiliate-skills/bonus-stack-builder

$npx -y skills add Affitor/affiliate-skills --skill bonus-stack-builder

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Bonus Stack Builder
2
3	Design exclusive bonus packages that make YOUR affiliate link the only rational choice. The product is the same through every affiliate's link — your bonuses are what differentiate you. Creates specific, deliverable bonuses matched to your skills and audience needs.
4
5	## Stage
6
7	S4: Landing — Bonuses live on the landing page. They are the conversion differentiator between your link and every other affiliate promoting the same product.
8
9	## When to Use
10
11	- User promotes an affiliate product and wants to stand out from other affiliates
12	- User asks "why would someone buy through MY link?"
13	- User wants to increase conversion rates on existing promotions
14	- User says "bonus", "bonus stack", "exclusive offer", "differentiate"
15	- After running `grand-slam-offer` to flesh out the bonus suggestions
16
17	## Input Schema
18
19	```yaml
20	product: # REQUIRED — the affiliate product
21	name: string # Product name
22	description: string # What it does
23	pricing: string # Product price
24	url: string # Affiliate link
25	tags: string[] # e.g., ["ai", "video", "saas"]
26
27	your_skills: string[] # OPTIONAL — what you can create/offer
28	# e.g., ["writing", "design", "coding", "consulting"]
29	# Default: inferred from context
30
31	audience_pain_points: string[] # OPTIONAL — biggest struggles of your audience
32	# Default: inferred from product category
33
34	existing_bonuses: string[] # OPTIONAL — bonuses you already offer
35	# Default: none
36	```
37
38	Chaining from S4 grand-slam-offer: If `grand-slam-offer` was run, use `offer_stack.bonuses` as starting point and flesh them out.
39
40	## Workflow
41
42	### Step 1: Gather Context
43
44	1. If product data available from chain, use directly. Otherwise `web_search` for product details.
45	2. Identify the product's top 3 pain points it solves
46	3. Identify the product's top 3 gaps (things users struggle with after buying)
47	4. Research: `"[product] complaints" OR "[product] struggles" OR "[product] learning curve"` to find bonus opportunities
48
49	### Step 2: Design Bonus Stack
50
51	Read `shared/references/offer-frameworks.md` for bonus types and rules.
52
53	For each bonus, define:
54	1. What it is — specific deliverable, not vague
55	2. What problem it solves — maps to a pain point or product gap
56	3. Format — PDF, video, template, spreadsheet, community access, call
57	4. Perceived value — what you'd charge if sold separately
58	5. Effort to create — low/medium/high (helps user prioritize)
59	6. Exclusivity — why this is ONLY available through your link
60
61	Design 5-7 bonuses across these tiers:
62	- Tier 1: Quick wins (low effort to create, high perceived value) — templates, checklists, swipe files
63	- Tier 2: Deep value (medium effort, high impact) — mini-course, workshop recording, tool
64	- Tier 3: Premium (high effort, ultimate differentiator) — personal support, community, coaching
65
66	### Step 3: Calculate Stack Value
67
68	- Sum perceived values of all bonuses
69	- Compare to product price — bonus value should be 3-10x product price
70	- Identify the "hero bonus" — the one that does the most persuasive heavy lifting
71
72	### Step 4: Write Bonus Copy
73
74	For each bonus, write:
75	- Name — specific and benefit-driven (not "Bonus #1")
76	- One-liner — what it is + what it does for them
77	- Value statement — "$XX value — FREE with your purchase"
78	- Delivery method — how they get it after purchasing
79
80	### Step 5: Self-Validation
81
82	- [ ] Each bonus is specific and deliverable (not vague promises)
83	- [ ] At least one bonus addresses the product's biggest gap
84	- [ ] Total bonus value exceeds product price
85	- [ ] At least one "exclusive" bonus (only through your link)
86	- [ ] All bonuses are within your skills to actually create
87	- [ ] No income claims or unrealistic promises
88
89	## Output Schema
90
91	```yaml
92	output_schema_version: "1.0.0"
93	bonus_stack:
94	product_name: string
95	total_value: string # Total perceived value of all bonuses
96	product_price: string # For comparison
97	hero_bonus: string # The most compelling bonus name
98	bonuses:
99	- name: string
100	description: string
101	problem_solved: string
102	format: string

People who liked this also viewed

6 picks

Type