offer-builder — Claude Code skill: offers and setup
The offer-builder Claude Code skill drafts a one-page offer with its price, delivery date, and refund terms. It activates on requests to write an offer, prepare a proposal, or answer a prospect asking for details.
MIT ★ 92 updated 2026-11-06
/plugin marketplace add Jakeschincariol/whale-skill
/plugin install whale-skill@whale-skillWhat offer-builder does
The skill turns deal details into an offer that states the buyer’s current costs, what they receive, the price, and the delivery date. It also says the product is unfinished and explains how the buyer can get a refund. The price comes from /pricing and the date from /pre-sale terms; draft refuses to proceed without them.
The offer.py script drafts the page, checks it with lint, and records an offer after it has been sent. The check rejects missing terms, invented urgency, and claims that cannot be backed up. Each offer needs a separate approval before sending. Python 3 is required; email sending uses Gmail or its connector, and payment links go through Stripe.
What it helps with
- draft a one-page offer from deal terms
- catch missing prices or delivery dates
- remove unsupported claims and fake urgency
- record an approved offer after it is sent
Example prompts for the agent
- Draft an offer for the
north-pierdeal from the demo call notes. - Check
whale/offers/north-pier.mdfor missing terms and claims we cannot support. - Record the sent offer for
north-pierafter I approve it.
How to install offer-builder
1Plugin marketplace
/plugin marketplace add Jakeschincariol/whale-skill/plugin install whale-skill@whale-skillThis installs the whole whale-skill plugin with all its skills
2Skills CLI (Vercel)
npx skills add Jakeschincariol/whale-skill --skill offer-builder -a claude-code3Manually: put the files in place
~/.claude/skills/offer-builder/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/offer-builder/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/whale-skill --skill offer-builder -a codex2Manually: put the files in place
.agents/skills/offer-builder/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/whale-skill --skill offer-builder -a cursor2Manually: put the files in place
.cursor/skills/offer-builder/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/whale-skill offer-builder2Manually: put the files in place
.github/skills/offer-builder/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/whale-skill --skill offer-builder -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/whale-skill --path offer-builderManually: put the files in place
.devin/skills/offer-builder/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about offer-builder
How do I install offer-builder in Claude Code?
Add the marketplace with /plugin marketplace add Jakeschincariol/whale-skill, then install the skill with /plugin install whale-skill@whale-skill.
What does offer-builder do?
It drafts a one-page offer with pricing, a delivery date, and refund terms, then checks for missing details and unsupported claims. Sending requires approval for that specific offer.
What does offer-builder need to run?
It requires Python 3 and configured /pricing and /pre-sale terms. Sending email uses Gmail or its connector, while payment links go through Stripe.
Source text
SKILL.md · MIT
---
name: offer-builder
description: >-
Offer Builder. Writes the offer they can say yes to. One page: the problem in their own numbers, what
they get, the price, the date it ships, and the way out, with the plain statement that it isn't finished
yet. A lint refuses an offer that leaves any of that out or that leans on fake urgency, made-up proof and
promises nobody can keep. Every offer waits for your yes. Use when the user says "write the offer", "make
them an offer", "offer page", "proposal", "one-pager", "what do I send them", "they asked for details",
or "founding customer offer".
argument-hint: "[draft <deal> | lint <file> | record <deal>]"
---
# 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).
```bash
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
1. **Today:** what they pay now for this, from the board. "$6,400 a month ($76,800 a year)."
2. **What it does,** in one line.
3. **What you get:** only what they told you they want (`--get`, repeat it). Never a padded feature list.
4. **The price:** from `/pricing`. One number, paid up front.
5. **When:** the ship date, from `/pre-sale terms`.
6. **What you should know:** it isn't finished, and how they get their money back.
7. **The next step:** say yes and you send the Stripe link.
## Steps
1. Check that `/pre-sale terms` is set and the deal has a price from `/pricing`. `draft` refuses without them.
2. `offer.py draft`. Read their words from the demo call and use them. Fill every `[fill: ...]`.
3. `offer.py lint`. Fix everything it finds. If a line isn't provable, it doesn't go in.
4. **Ask.** Show the page. "Send this to Renee Alvarez at North Pier Logistics? Reply yes or no." One offer per question, every time.
5. **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).
6. **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.
© Jake Schincariol · MIT · Jakeschincariol/whale-skill