jakeschincariol/founder-skill

founder-consumer

The consumer panel.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/jakeschincariol/founder-skill --skill founder-consumer

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

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.

dallo stesso repository

Altri Skills

Tutti gli Skills
jakeschincariol
Community

founder-brand

Your brand designer. Names the business (with the trademark, domain and handle checks to run before falling in love with a name), writes the voice, a one-line promise and a tagline, and briefs the look: colours, type, logo and the first things a customer sees, so they match the positioning the marketing director chose. Use when the user says "name my business", "brand this", "logo", "brand identity", "what should it look like", "tagline", or "brand voice".

Installazioni / 1h
1
GitHub Stars
4,4K
Aggiornato
7 ott
jakeschincariol
Community

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", "g

Installazioni / 1h
1
GitHub Stars
4,4K
Aggiornato
7 ott
jakeschincariol
Community

founder-launch

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".

Installazioni / 1h
4
GitHub Stars
4,4K
Aggiornato
7 ott
jakeschincariol
Community

founder-board

Your board of directors. Puts a business idea in front of a three-member board, each a sub-agent reading the idea through one published framework: the Offers lens (from Alex Hormozi's $100M Offers), the Monopoly lens (from Peter Thiel's Zero to One) and the Product lens (from Walter Isaacson's biography of Steve Jobs). Each member scores the idea, names the risks that would kill it and votes fund, fund with conditions, or pass. Use when the user says "test my business idea", "would this work", "

Installazioni / 1h
3
GitHub Stars
4,4K
Aggiornato
7 ott