offer-builder
A good offer takes one page and leaves no question open. The buyer should be able to forward it to their
boss with no explanation. This skill writes that page, and won't let it say anything you can't back up.
${CLAUDE_SKILL_DIR} below is this skill's folder (where this SKILL.md lives).
python3 "${CLAUDE_SKILL_DIR}/offer.py" draft --deal north-pier --get "Every late invoice chased automatically" \
--get "Built to your requirements, which we go through together after you pay"
python3 "${CLAUDE_SKILL_DIR}/offer.py" lint --offer whale/offers/north-pier.md
python3 "${CLAUDE_SKILL_DIR}/offer.py" record --deal north-pier --text-file whale/offers/north-pier.md \
--subject "Your Product: the offer" --approval "yes" --at 2026-11-02T10:15
What is on the page
- Today: what they pay now for this, from the board. "$6,400 a month ($76,800 a year)."
- What it does, in one line.
- What you get: only what they told you they want (
--get, repeat it). Never a padded feature list.
- The price: from
/pricing. One number, paid up front.
- When: the ship date, from
/pre-sale terms.
- What you should know: it isn't finished, and how they get their money back.
- The next step: say yes and you send the Stripe link.
Steps
- Check that
/pre-sale terms is set and the deal has a price from /pricing. draft refuses without them.
offer.py draft. Read their words from the demo call and use them. Fill every [fill: ...].
offer.py lint. Fix everything it finds. If a line isn't provable, it doesn't go in.
- Ask. Show the page. "Send this to Renee Alvarez at North Pier Logistics? Reply yes or no." One offer per question, every time.
- Send. On a yes, as a Gmail draft from the user's account, which the user sends (or through the Gmail connector right after that yes).
- Log. Only after it went out:
offer.py record --approval "<their yes, word for word>". The deal moves to offer-sent, and /follow-up
keeps it alive. When they say yes, /pre-sale link. When they push back, /objection-handler.
What lint refuses
- No price, no ship date, nothing saying it isn't finished, or no way to get their money back.
- Fake urgency: "act now", "limited time", "only 3 spots left", "last chance". If the price really does end, say the real date and why.
- Claims nobody can check: "guaranteed", "risk-free", "#1", "best in the industry", "trusted by", "thousands of customers".
- Anything still marked
[fill: ...].
Example from the reel
For North Pier Logistics: "Today you pay about $6,400 a month for invoice collections service ($76,800 a year)." Founding customer · 12 months,
$24,000.00, paid up front. Ships within 30 days of payment, built to your requirements. It isn't finished, and they get every dollar back if it
doesn't ship. (Illustrative: North Pier and every figure are fictional.)
What it never does
- Never sends, and never records an offer that did not go out.
- Never hides that the product isn't finished.
- Never invents a customer, a result, a discount or a deadline to make it feel urgent.
Consent and truth
- Nothing is sent or charged without the user's explicit yes for that exact offer. Claude drafts, the user says "yes", then it goes out from
the user's own accounts. One yes per message. Never "yes to all".
- Stop at the first "no" or any sign of disinterest. A request to stop is honoured forever, across every skill.
- Never invent a number, a result, a client or a deadline. An offer is a template, not legal advice: have a lawyer read your standard terms once.
1---2name: offer-builder3description: >-4 Offer Builder. Writes the offer they can say yes to. One page: the problem in their own numbers, what5 they get, the price, the date it ships, and the way out, with the plain statement that it isn't finished6 yet. A lint refuses an offer that leaves any of that out or that leans on fake urgency, made-up proof and7 promises nobody can keep. Every offer waits for your yes. Use when the user says "write the offer", "make8 them an offer", "offer page", "proposal", "one-pager", "what do I send them", "they asked for details",9 or "founding customer offer".10argument-hint: "[draft <deal> | lint <file> | record <deal>]"11metadata:12 source: https://skillmd.com/skills/jakeschincariol/offer-builder13---1415# offer-builder1617A good offer takes one page and leaves no question open. The buyer should be able to forward it to their18boss with no explanation. This skill writes that page, and won't let it say anything you can't back up.1920`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).2122```bash23python3 "${CLAUDE_SKILL_DIR}/offer.py" draft --deal north-pier --get "Every late invoice chased automatically" \24 --get "Built to your requirements, which we go through together after you pay"25python3 "${CLAUDE_SKILL_DIR}/offer.py" lint --offer whale/offers/north-pier.md26python3 "${CLAUDE_SKILL_DIR}/offer.py" record --deal north-pier --text-file whale/offers/north-pier.md \27 --subject "Your Product: the offer" --approval "yes" --at 2026-11-02T10:1528```2930## What is on the page31321. **Today:** what they pay now for this, from the board. "$6,400 a month ($76,800 a year)."332. **What it does,** in one line.343. **What you get:** only what they told you they want (`--get`, repeat it). Never a padded feature list.354. **The price:** from `/pricing`. One number, paid up front.365. **When:** the ship date, from `/pre-sale terms`.376. **What you should know:** it isn't finished, and how they get their money back.387. **The next step:** say yes and you send the Stripe link.3940## Steps41421. Check that `/pre-sale terms` is set and the deal has a price from `/pricing`. `draft` refuses without them.432. `offer.py draft`. Read their words from the demo call and use them. Fill every `[fill: ...]`.443. `offer.py lint`. Fix everything it finds. If a line isn't provable, it doesn't go in.454. **Ask.** Show the page. "Send this to Renee Alvarez at North Pier Logistics? Reply yes or no." One offer per question, every time.465. **Send.** On a yes, as a Gmail draft from the user's account, which the user sends (or through the Gmail connector right after that yes).476. **Log.** Only after it went out: `offer.py record --approval "<their yes, word for word>"`. The deal moves to `offer-sent`, and `/follow-up`48 keeps it alive. When they say yes, `/pre-sale link`. When they push back, `/objection-handler`.4950## What lint refuses5152- No price, no ship date, nothing saying it isn't finished, or no way to get their money back.53- Fake urgency: "act now", "limited time", "only 3 spots left", "last chance". If the price really does end, say the real date and why.54- Claims nobody can check: "guaranteed", "risk-free", "#1", "best in the industry", "trusted by", "thousands of customers".55- Anything still marked `[fill: ...]`.5657## Example from the reel5859For North Pier Logistics: "Today you pay about $6,400 a month for invoice collections service ($76,800 a year)." Founding customer · 12 months,60$24,000.00, paid up front. Ships within 30 days of payment, built to your requirements. It isn't finished, and they get every dollar back if it61doesn't ship. (Illustrative: North Pier and every figure are fictional.)6263## What it never does6465- Never sends, and never records an offer that did not go out.66- Never hides that the product isn't finished.67- Never invents a customer, a result, a discount or a deadline to make it feel urgent.6869## Consent and truth7071- Nothing is sent or charged without the user's explicit yes for that exact offer. Claude drafts, the user says "yes", then it goes out from72 the user's own accounts. One yes per message. Never "yes to all".73- Stop at the first "no" or any sign of disinterest. A request to stop is honoured forever, across every skill.74- Never invent a number, a result, a client or a deadline. An offer is a template, not legal advice: have a lawyer read your standard terms once.