offers
Skill870 starsChanged 3 months agoMITView on GitHub
When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.
We split this skill into the rules it gives an agent
4 rules. 3 are common, 0 are distinctive, and 1 is very specific to this project.
3
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older …
- Common: line 105
When the user says "my offer isn't converting" or "I want to improve my offer":
- Common: line 132
When drafting offer language (sales pages, emails, headlines), avoid:
- Common: line 140
Use specific numbers, named customers, concrete outcomes, real timelines.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Offer Design
You are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.
Before Starting
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Core Philosophy
The offer is the thing, not the page. Better copy on a weak offer compounds slowly. A stronger offer with average copy converts immediately. Most "we need better copy" requests are actually "we need a better offer" requests in disguise.
This skill exists because the rest of the repo handles the expression of an offer — copywriting writes the sales page, cro optimizes the conversion path, pricing sets the tier structure, launch orchestrates the moment, paywalls shapes the upgrade prompt. None of them ask the deeper question: is the offer underneath any of that actually good?
When this skill matters
You sell:
- Services — consulting, freelance, agency retainers, productized services
- Courses — async, cohort-based, live
- Coaching — 1:1, group, mastermind
- Info products — guides, swipe files, templates, communities
- High-ticket B2B — $5K+ ACV with a sales conversation
- Direct-response — e-com promo offers, infomercial-style, paid-traffic-to-VSL
When pricing does more of the work
You sell:
- Self-serve SaaS with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary
- Marketplaces — the offer is structural, not constructed
Skim this skill in those cases for the value equation framing, then go to pricing.
The Value Equation
The single most useful frame for offer design. Originally from Alex Hormozi's $100M Offers — internalized broadly across direct-response and creator-economy training since.
Dream Outcome × Perceived Likelihood of Achievement
Value = ─────────────────────────────────────────────────────────
Time Delay × Effort & SacrificeYou move the four levers like this:
| Lever | What it means | How to increase value |
| Dream outcome ↑ | What the customer actually wants | Connect to the bigger goal behind the surface ask. Specify and name it. |
| Perceived likelihood ↑ | Do they believe they'll get it | Proof (case studies, named customers, data), guarantees, methodology specificity |
| Time delay ↓ | How long until result | Faster onboarding, faster first win, faster end-to-end timeline |
| Effort & sacrifice ↓ | What it costs them in time/work/risk besides money | Done-for-you, simpler process, fewer decisions, lower learning curve |
Implication for offer construction: most "lower the price" requests are actually "raise the numerator or lower the denominator" requests. Price is the comparison, not the value.
For the full framework, examples, and how to diagnose which lever is broken: see references/value-equation.md
The Anatomy of a Complete Offer
A complete offer has six components. Skip any one and conversion suffers.
| # | Component | Question it answers |
| 1 | Core deliverable | What do they get? |
| 2 | Bonus stack | What else do they get that makes the core feel undervalued? |
| 3 | Guarantee | What happens if it doesn't work? |
| 4 | Scarcity / urgency | Why now, not later? |
| 5 | Name | What is this thing called? |
| 6 | Price + payment structure | What do they pay and how? |
Most weak offers fail on bonuses (none), guarantees (none or wrong type), or scarcity (none, or fake). Most aggressive-to-the-point-of-cringe offers fail on guarantee (over-promising) or scarcity (fake countdown timers).
For the full anatomy with worked examples: see references/offer-anatomy.md
Reference Library
| Reference | When to read |
| value-equation.md | Diagnosing which lever is broken on a stuck offer |
| offer-anatomy.md | Building a complete offer from scratch |
| guarantee-design.md | Picking the right type of guarantee for your business model |
| bonus-stacking.md | Adding bonuses that raise perceived value without devaluing the core |
| scarcity-urgency.md | Creating real scarcity (and avoiding the fake patterns that destroy trust) |
| offer-formats.md | Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B |
| examples.md | Anonymized worked examples — before/after for each business type |
The Diagnostic Loop
When the user says "my offer isn't converting" or "I want to improve my offer":
- Identify the business type — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.
- State the current offer in plain language — name, price, what they get, guarantee, deadline. Write it down even if it lives in scattered places now.
- Run the value equation — score each of the four levers 1–10. The lowest is the binding constraint.
- Audit the anatomy — which of the six components is missing or weak?
- Pick one lever to fix this iteration — don't rebuild everything. The biggest lever is usually the one currently scoring lowest.
- Draft the changed component — new bonus, new guarantee, new scarcity, new name, new payment plan
- Project the lift, honestly — most single-component changes deliver 10–40% conversion lift. Anyone promising 5x is selling something. Two consecutive iterations on different levers can stack to 2–3x.
When NOT to Use Offer-Design Tactics
Some offer patterns work but cost more than they're worth:
- Manipulative scarcity — fake countdown timers, "only 3 spots left" lies. Short-term lift, long-term trust collapse. Don't.
- Over-promising guarantees — "double your revenue or refund + $1,000." Refund risk eats margin; the few cases that fail nuke your reputation publicly.
- Bonus inflation — stacking $50K of "bonuses" on a $497 product so it "feels like a steal." Sophisticated buyers see this. Treat bonuses as additive, not exaggerated.
- Course-bro aesthetic on a serious product — Gold logos, "secret method," fake urgency. Pattern-matches to scam. Wrong room.
The repo voice: opinionated, but honest. Building offers well doesn't mean building offers loud.
Banned Vocabulary
When drafting offer language (sales pages, emails, headlines), avoid:
- "Game-changing," "revolutionary," "disruptive," "next-level," "10x" — pattern-matches to AI slop / course-bro
- "Secret," "hidden," "what they don't want you to know" — clickbait
- "Limited time" with no actual time limit — lying
- "Worth $X" or "$Y value" with no comparable — inflation
- "100% guaranteed" without specifying conditions — legally and brand-wise risky
Use specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives.
Related Skills
- pricing — for price levels, tier structure, value metric, packaging, freemium
- copywriting — for the page that presents the offer
- cro — for optimizing the conversion path the offer travels through
- launch — for the moment you ship the offer
- paywalls — for in-app upgrade-prompt versions of an offer
- sales-enablement — for the deck and one-pager that carry the offer into a sales conversation
- emails — for the email sequence that warms up the offer
- marketing-psychology — for the cognitive biases that make offers land or bounce
Other versions25 projects use a version of this.
Word for word · 14
- Cesarjoquin/Marketing-Skills★ 190100% same
- open-fox/agents★ 55100% same
- SZcalligrapher/slash-skills-subscription★ 32100% same
- TommyBez/skillsboard★ 10100% same
- agrivisionai/claude-skills★ 1100% same
- altrwork/skills★ 1100% same
- mahiunfiltered/claude-code-skills★ 1100% same
- ngothanhtung/claude-code-skills★ 1100% same
- productionx-in/Core-Skills★ 1100% same
- SkotAlexsander/skills★ 1100% same
4 more not listed
Edited · 10
- coreyhaines31/marketingskills★ 58k90% same
- anis-dr/skills★ 393% same
- patinaproject/skills★ 193% same
- claude1cryptwareinfotech-star/Claude-Skill★ 093% same
- GAPZ787/claude-skills★ 093% same
- Gopyr/gopyr-skills-hub★ 088% same
- jratlee/FDI★ 093% same
- masterpeteworld/claude-skills★ 093% same
- matheus-rib1108/meu-kit-claude-code★ 090% same
- salacoste/daytona-seo-notch★ 089% same
Wrote their own version · 1
- david-corroy/skills-marketing-fr★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use events, emil-design-eng and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agenkinSkillevents
Schema discovery — list every event name firing for the current TelemetryDeck app with 7-day and 30-day counts side by side.
Also in 4 projects that use this
VercelSkillemil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Also in 3 projects that use this
VercelSkillremotion-best-practices
Best practices for Remotion - Video creation in React
Also in 3 projects that use this
StrayDragonSkillui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Also in 3 projects that use this
In this repository30 other files it gives its agents.
- AGENTS.MDAGENTS.md
- ai-seoSkill
- analyticsSkill
- attributionSkill
- churn-preventionSkill
- co-marketingSkill
- community-marketingSkill
- competitor-profilingSkill
- competitorsSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- croSkill
- customer-researchSkill
- imageSkill
- influencer-marketingSkill
- launchSkill
- marketing-councilSkill
- marketing-ideasSkill
- marketing-loopsSkill
- marketing-planSkill
- marketing-psychologySkill
- onboardingSkill
- pricingSkill
- product-marketingSkill
- programmatic-seoSkill
- seo-auditSkill
- seoSkill
- site-architectureSkill
- videoSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

