Bonus Stack Builder

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 2515ce9634da · 15 Oct 2026Report an issue or request a re-scan

• PublisherAffitor GitHub organizationOwner of the repository this skill is read from
• Source folderAffitor/affiliate-skills/skills/landing/bonus-stack-builderThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict2515ce9634daA new audit runs when the source changes
• Repository statusNot archivedLast push 2 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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…

---
name: bonus-stack-builder
description: >
  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 bonuses", "bonus package",
  "what can I offer as a bonus", "design bonuses", "build a bonus stack".
license: MIT
version: "1.0.0"
tags: ["affiliate-marketing", "landing-pages", "conversion", "offers", "bonuses", "hormozi"]
compatibility: "Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent"
metadata:
  author: affitor
  version: "1.0"
  stage: S4-Landing
---

# Bonus Stack Builder

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.

## Stage

S4: Landing — Bonuses live on the landing page. They are the conversion differentiator between your link and every other affiliate promoting the same product.

## When to Use

- User promotes an affiliate product and wants to stand out from other affiliates
- User asks "why would someone buy through MY link?"
- User wants to increase conversion rates on existing promotions
- User says "bonus", "bonus stack", "exclusive offer", "differentiate"
- After running `grand-slam-offer` to flesh out the bonus suggestions

## Input Schema

```yaml
product:                    # REQUIRED — the affiliate product
  name: string              # Product name
  description: string       # What it does
  pricing: string           # Product price
  url: string               # Affiliate link
  tags: string[]            # e.g., ["ai", "video", "saas"]

your_skills: string[]       # OPTIONAL — what you can create/offer
                            # e.g., ["writing", "design", "coding", "consulting"]
                            # Default: inferred from context

audience_pain_points: string[] # OPTIONAL — biggest struggles of your audience
                               # Default: inferred from product category

existing_bonuses: string[]  # OPTIONAL — bonuses you already offer
                            # Default: none
```

**Chaining from S4 grand-slam-offer**: If `grand-slam-offer` was run, use `offer_stack.bonuses` as starting point and flesh them out.

## Workflow

### Step 1: Gather Context

1. If product data available from chain, use directly. Otherwise `web_search` for product details.
2. Identify the product's top 3 pain points it solves
3. Identify the product's top 3 gaps (things users struggle with after buying)
4. Research: `"[product] complaints" OR "[product] struggles" OR "[product] learning curve"` to find bonus opportunities

### Step 2: Design Bonus Stack

Read `shared/references/offer-frameworks.md` for bonus types and rules.

For each bonus, define:
1. **What it is** — specific deliverable, not vague
2. **What problem it solves** — maps to a pain point or product gap
3. **Format** — PDF, video, template, spreadsheet, community access, call
4. **Perceived value** — what you'd charge if sold separately
5. **Effort to create** — low/medium/high (helps user prioritize)
6. **Exclusivity** — why this is ONLY available through your link

Design 5-7 bonuses across these tiers:
- **Tier 1: Quick wins** (low effort to create, high perceived value) — templates, checklists, swipe files
- **Tier 2: Deep value** (medium effort, high impact) — mini-course, workshop recording, tool
- **Tier 3: Premium** (high effort, ultimate differentiator) — personal support, community, coaching

### Step 3: Calculate Stack Value

- Sum perceived values of all bonuses
- Compare to product price — bonus value should be 3-10x product price
- Identify the "hero bonus" — the one that does the most persuasive heavy lifting

### Step 4: Write Bonus Copy

For each bonus, write:
- **Name** — specific and benefit-driven (not "Bonus #1")
- **One-liner** — what it is + what it does for them
- **Value statement** — "$XX value — FREE with your purchase"
- **Delivery method** — how they get it after purchasing

### Step 5: Self-Validation

- [ ] Each bonus is specific and deliverable (not vague promises)
- [ ] At least one bonus addresses the product's biggest gap
- [ ] Total bonus value exceeds product price
- [ ] At least one "exclusive" bonus (only through your link)
- [ ] All bonuses are within your skills to actually create
- [ ] No income claims or unrealistic promises

## Output Schema

```yaml
output_schema_version: "1.0.0"
bonus_stack:
  product_name: string
  total_value: string          # Total perceived value of all bonuses
  product_price: string        # For comparison
  hero_bonus: string           # The most compelling bonus name
  bonuses:
    - name: string
      description: string
      problem_solved: string
      format: string           # "pdf" | "video" | "template" | "community" | "call" | "tool"
      perceived_value: string
      effort_to_create: string # "low" | "medium" | "high"
      exclusivity: string
      delivery: string         # How they receive it

chain_metadata:
  skill_slug: "bonus-stack-builder"
  stage: "landing"
  timestamp: string
  suggested_next:
    - "landing-page-creator"
    - "guarantee-generator"
    - "email-drip-sequence"
```

## Output Format

```
## Bonus Stack: [Product Name]

### Stack Overview
- **Product price:** $XX/mo
- **Total bonus value:** $XXX
- **Hero bonus:** [name]
- **Message:** "Get $XXX in exclusive bonuses FREE when you start [product] through my link"

### Bonus 1: [Name] ($XX value)
**What:** [specific deliverable]
**Solves:** [pain point]
**Format:** [format]
**Delivery:** [how they get it]
**Why exclusive:** [only through your link because...]

[Repeat for each bonus]

### Bonus Copy (ready to paste)

✅ [Bonus 1 name] — [one-liner] ($XX value)
✅ [Bonus 2 name] 

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-15
   ✓SAFE B 89 / 100

   first audit · source 2515ce9634da

Questions about Bonus Stack Builder

• github.com/Affitor/affiliate-skills/tree/main/skills/landing/bon — the audited source at commit 2515ce9634da and every finding aboveObserved · 15 Oct 2026

Spotted something wrong? Report a correction · Methodology