offer-design
Skill43 starsChanged 4 months agoMITView on GitHub
Use when designing or improving an offer, package, pricing page argument, plan structure, guarantee, bonus, trial, annual discount, service bundle, or upgrade path.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Keremozdemirra/strategy-agenttheir own version, first seen Oct 20, 2026
- 808enzo/chappietheir own version, first seen Sep 17, 2026
- moronireis/agent-system-partnerstheir own version, first seen Sep 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- 808enzo/chappie★ 3same name
- Keremozdemirra/strategy-agent★ 0same name
- moronireis/agent-system-partners★ 0same 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.
In this repository25 other files it gives its agents.
- ab-testingSkill
- ai-seoSkill
- analytics-trackingSkill
- cold-outreachSkill
- competitor-analysisSkill
- content-strategySkill
- copywritingSkill
- creative-briefSkill
- cro-auditSkill
- customer-researchSkill
- distribution-planSkill
- ecommerce-app-croSkill
- email-sequenceSkill
- goalSkill
- launch-loop-strategySkill
- launch-strategySkill
- marketing-briefSkill
- marketing-planSkill
- paid-adsSkill
- partnershipsSkill
- positioningSkill
- retentionSkill
- sales-enablementSkill
- seo-strategySkill
- x-article-writerSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
If the user asks for copy before the offer is clear, define the offer first.
- Distinctive: line 52
Do not invent scarcity.
- Distinctive: line 53
Do not recommend a guarantee the business cannot honor.
- Distinctive: line 55
Use a value metric customers can understand and the business can support.
- Distinctive: line 56
Keep plan differences based on customer maturity or usage, not arbitrary feature hiding.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Shape the offer around buyer anxiety, adoption path, fulfillment constraints, and plan boundaries.
Understand The Sale
Identify:
- Buyer and user.
- Desired outcome.
- Current alternative.
- Price or expected budget.
- Purchase anxiety.
- Fulfillment cost and margin risk.
- Proof available.
- Sales motion: self-serve, sales-led, product-led, service-led, marketplace.
If the user asks for copy before the offer is clear, define the offer first.
Inspect Offer Fit
Break it into fit dimensions:
- Buyer anxiety: what makes the purchase feel risky.
- Adoption path: what has to happen after purchase for value to appear.
- Fulfillment constraint: what the business must deliver reliably.
- Support burden: where customers will need help.
- Abuse risk: how guarantees, trials, discounts, or unlimited use can be misused.
- Plan boundary: what separates small, growing, and high-value customers.
- Proof threshold: what evidence the buyer needs before paying.
- Price logic: how price maps to value, usage, or urgency.
Flag weak spots: vague deliverables, fake urgency, unpriced complexity, guarantees that create abuse, discounts that train waiting, support promises the team cannot honor, or plan tiers that punish the best customers.
Redesign
Offer 2-3 structures:
- Simple offer: easiest to understand and buy.
- Proof-heavy offer: best when trust is the barrier.
- Expansion offer: best when land-and-expand matters.
For each, define the promise, included pieces, exclusions, price logic, risk reversal, and reason to act now.
Watch Outs
- Do not invent scarcity.
- Do not recommend a guarantee the business cannot honor.
- Tie bonuses to purchase anxiety, not random perceived value.
- Use a value metric customers can understand and the business can support.
- Keep plan differences based on customer maturity or usage, not arbitrary feature hiding.
Output
Offer fit diagnosis:
[what is clear, what is weak]
Purchase anxiety:
- [fear]
- [fear]
Recommended offer:
Name:
For:
Promise:
Includes:
Excludes:
Price logic:
Adoption support:
Risk handling:
Abuse boundary:
Plan boundary:
Alternative structures:
1. [option] - [when to use]
2. [option] - [when to use]
Copy-ready bullets:
- [bullet]
- [bullet]
- [bullet]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.

