founder-consumer — Claude Code skill: what it does, how to install
The founder-consumer Claude Code skill simulates buyer reactions to a pitch and groups responses by customer segment. It runs when asked to test demand or identify likely buyers.
MIT 739 installs ★ 4,548 updated 2026-10-07
npx skills add Jakeschincariol/founder-skill --skill founder-consumer -a claude-codeWhat founder-consumer does
The skill builds a target-customer profile, gives simulated buyers the same pitch, then summarizes who would buy, what objections they raise, and how they respond to different prices. It writes its working files and results to founder/customer.json, founder/pitch.md, and founder/panel/.
The panel requires Python 3 and Claude Code’s Agent tool; older versions call it Task. A standard run uses 100 sub-agents, while --quick uses 20. These buyers are simulated by a language model, whose agreeable responses can make the buy rate higher than real-world conversion. Panel answers are not customer testimonials.
What it helps with
- gauge buyer reactions to a product pitch
- compare interest across customer segments
- collect reasons buyers reject an offer
- find changes that could shift a buyer’s decision
- gather buyer responses to pricing
Example prompts for the agent
- Run a buyer panel for this idea and show me who would buy.
- Test this offer with target customers and summarize why they might pass.
- Simulate buyers and report how they react to the price.
How to install founder-consumer
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-consumer -a claude-code2Manually: put the files in place
~/.claude/skills/founder-consumer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/founder-consumer/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-consumer -a codex2Manually: put the files in place
.agents/skills/founder-consumer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-consumer -a cursor2Manually: put the files in place
.cursor/skills/founder-consumer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/founder-skill skills/founder-consumer2Manually: put the files in place
.github/skills/founder-consumer/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-consumer -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/founder-skill --path skills/founder-consumerManually: put the files in place
.devin/skills/founder-consumer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jakeschincariol/founder-skill --skill founder-consumer -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-consumer
How do I install founder-consumer in Claude Code?
Run npx skills add Jakeschincariol/founder-skill --skill founder-consumer -a claude-code. The skill is installed at ~/.claude/skills/founder-consumer/SKILL.md.
What does founder-consumer do?
It simulates buyers with different profiles and responses to a pitch, then groups the results by segment. The report covers purchase interest, objections, possible reasons to change a decision, and price responses.
Can founder-consumer predict actual sales conversion?
No: its buyers are language-model simulations, and agreeable responses can inflate the buy rate. Treat the results as simulated feedback, not real customer testimonials or a conversion forecast.
Source text
SKILL.md · MIT
---
name: founder-consumer
description: >-
The consumer panel. Spins up a swarm of buyer sub-agents (default 100, --quick
for 20) trained on the user's target customer, each with a different income,
age, buying behaviour and objection, shows every one the same pitch, and runs
the business through 100 buyer scenarios to see who buys, who doesn't, and why.
Tallies the answers into buy rates by segment, the reasons people pass in their
own words, what would flip a no, and price answers for founder-pricing. Use when
the user says "would people buy this", "test it on customers", "run the
consumer panel", "simulate buyers", "who is my customer", or "validate demand".
argument-hint: "[--n 100 | --quick] [--seed S]"
---
# founder-consumer
The craziest part of the pack. Instead of guessing whether people will buy, you
ask a hundred of them, each one a sub-agent playing a specific buyer drawn from
your target customer. You are the moderator. You never answer for a buyer.
What the user typed after `/founder-consumer`: `$ARGUMENTS`
## The tool
All bookkeeping goes through `panel.py` in this skill's folder:
```bash
python3 "${CLAUDE_SKILL_DIR}/panel.py" <command>
```
Below, `PANEL` means exactly that. If the path is not expanded, use the base
directory Claude Code printed for this skill. State lives in `founder/panel/`.
## Step 1: the target customer
Write `founder/customer.json` (shape: `customer.example.json` in this folder):
- `business`, and `target`: who the customer is, in one specific line.
- `segments`: 2 to 4 groups with a `share` and an `income` range [low, high].
- `behaviours`: 4 to 8 buying behaviours with a `share` and a `how` line
(daily regular, deal hunter, reads every review, loyal to a competitor...).
- `objections`: the 4 to 8 doubts this kind of buyer really has.
- `habits` (optional): everyday context lines that make a buyer concrete.
Ground it in something real. Use what the user knows about their customers, and
if `/founder-competitors` ran, the complaints in `founder/competitors.md`. If the
user has real customer data (interviews, reviews, survey answers), prefer it to
your guesses and say which parts are guesses. Show the user the profile in a few
lines and let them correct it before you deal: a wrong customer makes the whole
panel wrong.
## Step 2: the pitch
Write `founder/pitch.md`: what a buyer would actually see. The product, the price,
where and how to get it, any opening offer. Three to six plain lines, no
superlatives, nothing the business cannot deliver. Every buyer sees exactly this.
## Step 3: deal and run
```bash
PANEL init --customer founder/customer.json --pitch founder/pitch.md --n 100
PANEL prompts
```
`init` deals the persona cards (same seed, same cards; the seed is recorded).
`prompts` writes one brief per buyer and lists them in waves of 10. For each wave,
send ONE message with one Agent tool call per buyer in that wave (the Agent tool
is called Task in older Claude Code versions):
- `subagent_type`: `general-purpose`
- `description`: `panel <id>`
- `prompt`: `Read <brief path> and follow it exactly. It is your whole brief.`
Wait for the whole wave before the next one. Claude Code runs about 10 tool calls
at once by default, so 100 buyers is 10 waves. After the last wave:
```bash
PANEL check # lists missing or broken answers
PANEL prompts # rewrites briefs for those only; run them once more
PANEL tally
```
If a buyer printed its JSON in its reply instead of writing the file (it happens),
file its own reply with `PANEL save <id>` and the reply on stdin; `save` refuses
anything that is not a valid answer. A buyer that fails twice is left out and
counted in the results. Never write an answer for a buyer yourself.
Before a 100-buyer run, tell the user it is 100 sub-agent calls and suggest
`--quick` (20 buyers) for a first look. Sub-agents write one file each into
`founder/panel/answers/`; in the default permission mode that is one approval per
file, so suggest accept-edits mode (Shift+Tab) for the run.
## Step 4: read it to the user
`PANEL tally` writes `founder/panel/results.md` and `results.json`. Give the user:
1. The headline: "40 buy · 60 pass" and the buy rate.
2. Who buys and who doesn't: the segment and behaviour rows that differ most.
3. Why they pass: the top three reasons with one quote each, as written.
4. What would flip a no: the most repeated answers.
5. One sentence on what to change before spending money, and which skill does it
(pricing, offer, marketing).
## Honest limits, say them once
These are simulated buyers. They are good at surfacing objections, segments and
wording you had not thought of, and bad at predicting real conversion: language
models lean agreeable, so treat the buy rate as an upper bound. Confirm the big
calls with real people (a waitlist, a pre-sale, a landing page with a price)
before signing anything. Do not present panel quotes as customer testimonials.
## The brief every buyer gets
`panel.py` fills the card into a fixed template (see `BRIEF` in the script): who
the buyer is (name, age, segment, income, buying behaviour, a habit, the doubt
that comes to mind), the pitch word for word, an instruction not to be agreeable
and not to invent facts, and the exact JSON to write: buys, purchases in the first
month, a reason code, the reason in their own voice, their main objection, what
would change their mind, and four price answers (too cheap, a bargain, getting
expensive, too expensive). Never edit a brief for one buyer.
## Output
`founder/customer.json`, `founder/pitch.md`, `founder/panel/` (cards, briefs,
answers, results). Next: `/founder-pricing` reads the price answers,
`/founder-offer` and `/founder-marketing` read the objections.
© Jakeschincariol · MIT · Jakeschincariol/founder-skill