grand-slam-offer
Design irresistible affiliate offers using the Hormozi Grand Slam framework. Triggers on: "create an offer for", "design my offer", "grand slam offer", "make an irresistible offer", "why should someone buy through my link", "offer framework", "value proposition for", "Hormozi offer", "offer stack", "make my offer irresistible", "craft an offer", "what makes my offer different", "offer design", "increase perceived value".
What this skill does
# Grand Slam Offer
Design affiliate offers so good people feel stupid saying no. Uses the Hormozi Value Equation: **Value = Dream Outcome × Perceived Likelihood ÷ Time Delay ÷ Effort & Sacrifice**. Deconstructs why someone should click YOUR link over any other affiliate's.
## Stage
S4: Landing — The offer IS the landing page's job. Before writing HTML or copy, you need an offer framework that makes the conversion inevitable.
## When to Use
- User wants to differentiate their affiliate promotion from every other affiliate
- User asks "why would someone buy through MY link?"
- User is about to create a landing page and needs the offer angle first
- User wants to increase conversion rates on an existing promotion
- User says anything like "offer", "value proposition", "irresistible", "Hormozi"
- User has a product from S1 and wants to craft the positioning before S4 landing page
## Input Schema
```yaml
product: # REQUIRED — the affiliate product
name: string # Product name
description: string # What it does
reward_value: string # Commission (e.g., "30% recurring")
url: string # Affiliate link URL
pricing: string # Product price or pricing page URL
tags: string[] # e.g., ["ai", "video", "saas"]
target_audience: string # OPTIONAL — who you're targeting
# Default: inferred from product tags
bonuses: string[] # OPTIONAL — bonuses you're already offering
# Default: none (will suggest bonuses)
competitors: string[] # OPTIONAL — competing products
# Default: auto-researched
```
**Chaining from S1**: If `affiliate-program-search` was run earlier, automatically pick up `recommended_program` as the `product` input.
**Chaining from S1 purple-cow-audit**: If `purple-cow-audit` was run, use `remarkability_score` and `remarkable_angles` to inform the offer.
## Workflow
### Step 1: Gather Context
If product data is available from S1 chaining, use it directly. Otherwise:
1. Use `web_search` to research: `"[product name] features pricing review"`
2. Gather: name, pricing tiers, key features, target audience, top 3 competitors
3. If `target_audience` not provided, infer from product positioning and tags
### Step 2: Apply Value Equation
Read `shared/references/offer-frameworks.md` for the Hormozi framework.
For each component of the Value Equation, score the product 1-10 and identify leverage points:
**Dream Outcome (maximize)**
- What is the #1 transformation the audience wants?
- What does life look like AFTER using this product?
- Frame in terms of identity: "Become the person who..."
**Perceived Likelihood (maximize)**
- What proof exists? (case studies, user count, reviews)
- What specific numbers can you cite?
- What demonstration can you offer? (your own results, screenshots)
**Time Delay (minimize)**
- How fast can they see first results?
- What quick wins does the product offer?
- Can you accelerate with your bonuses? (templates, setup guide)
**Effort & Sacrifice (minimize)**
- What's the learning curve?
- What do they have to give up?
- Can you reduce effort with done-for-you assets?
### Step 3: Design the Offer Stack
Build the complete offer:
1. **Core product** — the affiliate product itself with reframed positioning
2. **Your unique angle** — why YOU are the right person to recommend this
3. **Bonus suggestions** — 3-5 bonuses that address the weakest Value Equation components
4. **Guarantee suggestion** — your personal guarantee on top of the product's
5. **Urgency element** — ethical, real urgency (if applicable)
### Step 4: Write Offer Copy
Create ready-to-use copy blocks:
- **Headline**: One sentence that captures the dream outcome
- **Sub-headline**: Addresses the biggest objection
- **Value stack**: Bullet list of everything they get (product + bonuses + guarantee)
- **CTA**: Action-oriented, specific, urgent
### Step 5: Output
Present the complete Grand Slam Offer framework.
### Step 6: Self-Validation
Before presenting output, verify:
- [ ] Value Equation is complete (all 4 components scored and addressed)
- [ ] Offer is differentiated from a generic "buy through my link" promotion
- [ ] Bonuses are specific and deliverable (not vague promises)
- [ ] Guarantee is realistic and scoped to what YOU can deliver
- [ ] Copy is specific to this product (not generic template fill)
- [ ] FTC-compliant — no income claims, no fake urgency
If any check fails, fix before delivering.
## Output Schema
```yaml
output_schema_version: "1.0.0"
grand_slam_offer:
product_name: string # Product being promoted
value_equation:
dream_outcome: string # The transformation promise
dream_outcome_score: number # 1-10
likelihood: string # Proof points
likelihood_score: number # 1-10
time_delay: string # Speed to results
time_delay_score: number # 1-10 (lower = better, inverted in output)
effort: string # Ease of use
effort_score: number # 1-10 (lower = better, inverted in output)
total_value_score: number # Calculated composite
offer_stack:
unique_angle: string # Your differentiator
bonuses: object[] # Suggested bonuses
guarantee: string # Your personal guarantee
urgency: string # Ethical urgency element
offer_copy:
headline: string # Main headline
sub_headline: string # Objection-addressing sub-headline
value_stack: string[] # Bullet list of everything included
cta: string # Call to action text
chain_metadata:
skill_slug: "grand-slam-offer"
stage: "landing"
timestamp: string
suggested_next:
- "landing-page-creator"
- "bonus-stack-builder"
- "guarantee-generator"
- "email-drip-sequence"
```
## Output Format
```
## Grand Slam Offer: [Product Name]
### Value Equation Analysis
| Component | Score | Leverage Point |
|---|---|---|
| Dream Outcome | X/10 | [key insight] |
| Perceived Likelihood | X/10 | [key insight] |
| Time Delay | X/10 | [key insight] |
| Effort & Sacrifice | X/10 | [key insight] |
| **Total Value Score** | **X/40** | |
### Your Unique Angle
[Why YOUR recommendation matters]
### Offer Stack
**They get:**
1. [Product] — [reframed benefit] ($XX/mo value)
2. BONUS: [Bonus 1] — [what it solves] ($XX value)
3. BONUS: [Bonus 2] — [what it solves] ($XX value)
4. BONUS: [Bonus 3] — [what it solves] ($XX value)
5. YOUR GUARANTEE: [guarantee statement]
**Total value: $XXX — they pay: $XX/mo**
### Ready-to-Use Copy
**Headline:** [headline]
**Sub-headline:** [sub-headline]
**Value Stack:**
[bullet list]
**CTA:** [call to action]
### Next Steps
- Run `bonus-stack-builder` to flesh out bonus details
- Run `guarantee-generator` to craft your guarantee copy
- Run `landing-page-creator` to build the page with this offer
```
## Error Handling
- **No product provided**: "I need a product to design an offer for. Run `affiliate-program-search` first, or tell me the product name."
- **No pricing found**: Use `web_search` for `"[product] pricing"`. If unavailable, use "Check current pricing" and frame value around ROI instead.
- **Product too generic**: "This product competes in a crowded space. Let me find your unique angle..." → focus on YOUR differentiators (bonuses, expertise, guarantee).
- **No competitive data**: Design the offer based on the product alone. Note: "Run `competitor-spy` for competitive intelligence to sharpen this offer."
## Examples
**Example 1:** "Design a grand slam offer for HeyGen"
→ Research HeyGen features/pricing, score Value Equation, identify unique angle (e.g., "AI video for non-creators"), suggest bonuses (script templates, avatar setup guide, prompt library), write offer copy.
**Example 2:** "I promote Semrush but my conversion rate is low"
→ Analyze why: likely weak differentiation. Score Value Equation, Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.