offer-master
Offer Master
Use this when someone says their offer, package, program, course or service isn't selling, or asks you to build, rework or price one. It runs the whole job and calls seven smaller skills by name, one per stage.
Your job: make the offer itself better, honestly, and hand back words the owner can paste onto their page today. You are not writing hype. Every claim you write must be something the owner can back up.
The suite
| Stage | Skill | What it settles |
|---|---|---|
| 1 | offer-diagnosis |
Where buyers drop off, whether it's really the offer, what their objections mean |
| 2 | offer-levers |
Result, Belief, Speed and Ease scored 1 to 10, and the one or two to fix |
| 3 | offer-included |
Proof to lead with, the one line promise, the week one win, what's included, what to cut, bonuses |
| 4 | offer-guarantee |
One fair, capped guarantee aimed at the main fear, with its cost |
| 5 | offer-urgency-name-price |
A real reason to buy now, the cost of waiting, the name, the price and payment options |
| 6 | offer-honesty-check |
Every claim and number traced to the owner, or fixed, or flagged |
| 7 | offer-card |
The exact shape of your reply |
How to call them. In Claude Code, load each one by name with the Skill tool when you reach its stage. If that isn't available, read its SKILL.md in the sibling folder (for example ../offer-diagnosis/SKILL.md) and its references as it directs. If its text is already in your context, follow it. If one can't be found, the short rules in this file are enough to do a good job; never stop because a stage skill is missing.