
founder-offer
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.
- Installs
- 328
- Last 24h
- +27
- Trending rank
- #4717
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jakeschincariol/founder-skill --skill founder-offer- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads founder-offer automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.mdandfounder/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.
FAQ
What does the founder-offer skill do?
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.
How do I install founder-offer?
Run npx skills add https://github.com/jakeschincariol/founder-skill --skill founder-offer in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/founder-offer/ (personal) or .claude/skills/founder-offer/ (project).
Which AI agents can use founder-offer?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is founder-offer safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains founder-offer?
It is published by jakeschincariol in jakeschincariol/founder-skill. It has 328 recorded installs.
More from jakeschincariol/founder-skill
founder-cfo
jakeschincariol/founder-skill
Your CFO. Builds the unit economics of a business before money is spent: what one unit earns after its direct costs, the real profit margin at the planned volume, the break-even point in units a day, year 1 month by month, the cash needed before it pays for itself, how long the startup spend takes to earn back, and what happens if the price drops, sales come in low or costs rise. Every number traces to an input the user can check. Use when the user says "find the profit margins", "do the numbers", "is this profitable", "break-even", "unit economics", "how much do I need to start", or "run the CFO".
founder-competitors
jakeschincariol/founder-skill
Maps every competitor and the gap they leave. Finds the direct competitors, indirect ones and the substitutes a buyer would use instead, from public sources only, and records what each sells, at what price, how they position themselves and what their customers complain about in public reviews, every fact with a link. Ends with a positioning map and the gap the new business can own. Use when the user says "who are my competitors", "is this market crowded", "what else is out there", "competitor analysis", "find the gap", or "who am I up against".
founder-consumer
jakeschincariol/founder-skill
Open the skill to read its SKILL.md instructions.
founder-plan
jakeschincariol/founder-skill
Your business planner. Compiles everything the other founder skills wrote (the board's verdict, the competitors, the buyer panel, pricing, the offer, the CFO's numbers, marketing, brand, operations and the launch plan) into one business plan with a verdict at the top that is computed from the numbers, never written by hand: Profitable, Not yet (with the failing numbers) or Incomplete. Adds an executive summary and a one-page version for a partner, lender or investor. Use when the user says "write my business plan", "put it all together", "is it profitable", "give me the plan", or at the end of the founder pack.
founder-launch
jakeschincariol/founder-skill
Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run sheet, and the first 30 days of what to measure and what to change. Use when the user says "how do I launch", "launch plan", "when can I open", "launch checklist", "go live", or "soft open".
founder-pricing
jakeschincariol/founder-skill
Open the skill to read its SKILL.md instructions.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work