founder-offer — Claude Code skill: build and test an offer
The founder-offer Claude Code skill shapes a sales offer around buyer problems and rates its value. It activates when a user wants to improve an offer or understand why buyers decline.
MIT 723 installs ★ 4,548 updated 2026-10-07
npx skills add Jakeschincariol/founder-skill --skill founder-offer -a claude-codeWhat founder-offer does
The skill maps obstacles buyers face to possible solutions, then assembles an offer with a core product, bonuses, a guarantee, genuine urgency and a name. Each proposed element is rated for buyer value and delivery cost. It rules out fabricated reviews and scarcity.
It writes the result to founder/offer.md and updates founder/pitch.md, preserving the previous pitch as founder/pitch-v1.md. It then runs /founder-consumer --quick with the same seed and compares the buy rate and buyer objections. Pricing a guarantee requires the CFO’s tool; the skill also reads founder/idea.md, founder/pitch.md, founder/panel/results.md, founder/numbers.json and founder/board.md.
What it helps with
- turn buyer objections into offer components
- weigh proposed solutions by buyer value and delivery cost
- compare buyer responses to revised and previous offers
- shape a guarantee around its estimated claim cost
Example prompts for the agent
- Improve my offer for [what you sell] and address the buyer objections.
- Why are buyers passing on [what you sell]? Rework the offer.
- What should I include in an offer for [what you sell] to answer the panel's objections?
How to install founder-offer
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-offer -a claude-code2Manually: put the files in place
~/.claude/skills/founder-offer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/founder-offer/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-offer -a codex2Manually: put the files in place
.agents/skills/founder-offer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-offer -a cursor2Manually: put the files in place
.cursor/skills/founder-offer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/founder-skill skills/founder-offer2Manually: put the files in place
.github/skills/founder-offer/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-offer -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/founder-skill --path skills/founder-offerManually: put the files in place
.devin/skills/founder-offer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-offer -a opencodeClaude.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 founder-offer
How do I install founder-offer in Claude Code?
Run npx skills add Jakeschincariol/founder-skill --skill founder-offer -a claude-code. The skill file is installed at ~/.claude/skills/founder-offer/SKILL.md.
What does founder-offer do?
It turns buyer obstacles into offer components, rates them by customer value and delivery cost, then retests the revised pitch with a quick buyer panel.
How does founder-offer retest a revised offer?
It runs /founder-consumer --quick with the same seed and compares the buy rate and objections. The new pitch goes into founder/pitch.md, while the previous version is kept as founder/pitch-v1.md.
Source text
SKILL.md · MIT
--- name: founder-offer description: >- Builds an offer too good to refuse. Lists every problem the buyer hits on the way to the result they want, turns each into a solution, trims to what is cheap to deliver and valuable to the buyer, and stacks it with honest bonuses, a guarantee the CFO can afford, real urgency and a clear name. Scores it on the value equation (outcome, likelihood, time, effort) and re-tests it on a quick buyer panel. Use when the user says "make my offer better", "why won't people buy", "what should I include", "guarantee", "bonuses", "grand slam offer", or after the panel shows people passing. argument-hint: "[what you sell]" --- # founder-offer Most businesses sell a product. Good ones sell an offer: the product plus everything that makes buying it an easy yes. This skill builds that, using the Offers lens in `../founder-board/lenses.md` as the method (a summary of the framework in Alex Hormozi's *$100M Offers*; never present it as his words). ## Step 1: read what is already known - `founder/idea.md` and `founder/pitch.md`: what is sold today. - `founder/panel/results.md`: why buyers pass, in their words. This is the raw material: every top objection should be answered by something in the offer. - `founder/numbers.json`: what each extra costs, so the stack stays profitable. - `founder/board.md`: the board's conditions. ## Step 2: the problem list Write every obstacle between the buyer and the result they want, in the buyer's words: before buying (doubt, price, effort to switch), during (waiting, learning, inconvenience), after (does it last, what if it fails). Aim for 15 to 30. Pull from the panel objections and the competitor complaints first. ## Step 3: solutions, trimmed and stacked Turn each problem into a solution (a feature, a service, a guarantee, a format). Score each on value to the buyer (1 to 5) and cost to deliver (1 to 5, from the CFO's numbers). Keep high value, low cost. Stack what is left into: - **The core**: the thing itself, described by the outcome, not the ingredients. - **Bonuses**: two or three, each killing one specific objection. - **The guarantee**: what happens if it does not deliver. Model what it costs at a realistic claim rate with the CFO's tool before promising it. - **Urgency and scarcity**: only if they are true (a launch week, a limited first batch). Never fake a countdown or a "only 3 left". - **The name**: a clear, specific name for the offer, not the company. ## Step 4: score it On the value equation, before and after, 1 to 10 each: dream outcome, perceived likelihood of getting it, time to the result, effort and sacrifice. Say which element of the stack moves which score. ## Step 5: re-test it Write the new offer into `founder/pitch.md` (keep the old one as `founder/pitch-v1.md`) and run `/founder-consumer --quick` with the same seed. Report the buy rate before and after and which objections dropped. If nothing moved, say so: the problem may be the market or the price, not the offer. ## Rules - Every promise must be deliverable and affordable; check costs with the CFO. - No fake reviews, testimonials, scarcity, discounts or "as seen on". - Follow the advertising and consumer-protection rules of the user's market for guarantees and claims (health claims especially). Not legal advice. ## Output `founder/offer.md` (problem list, the stack, costs, the value-equation scores, the re-test result) and the updated `founder/pitch.md`. Next: `/founder-cfo` to re-run the numbers with the stack, then `/founder-marketing`.
© Jakeschincariol · MIT · Jakeschincariol/founder-skill