← Back to list
🛠️

founder-board Checked

Your board of directors. Puts a business idea in front of a three-member board, each a sub-agent …
🛠️ Developer Tools skills By Jakeschincariol Version v1.0.0 Added 2026-10-12 Updated 2026-10-12 Source ↗
9.2Overall rating
0Views
0Downloads
313Stars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "founder-board" skill by following the instructions at https://skill123.me/install/founder-board.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/founder-board.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 4 KB
📊 Static rating
9.2/10
Trigger
8.0
Structure
8.7
Workflow
9.2
Content
10.0
Engineering
10.0
Security
10.0

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

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", "pressure-test this", "what would a board say", "is this a good business", or starts the founder pack on a new idea.

founder-board

The first meeting. Before anyone builds a website or signs a lease, three board

members tear the idea apart, each from a different angle, and vote.

What the user typed after /founder-board: $ARGUMENTS. If that is blank, take

the idea from the conversation.

Documentation

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", "pressure-test this", "what would a board say", "is this a good business", or starts the founder pack on a new idea.

founder-board

The first meeting. Before anyone builds a website or signs a lease, three board

members tear the idea apart, each from a different angle, and vote.

What the user typed after /founder-board: $ARGUMENTS. If that is blank, take

the idea from the conversation.

The rule about the three names

The lenses are summaries of **published frameworks**, nothing more. The board

members are not those people, never speak as them, never quote them, never claim

they would endorse anything. Write "the Offers lens", never "Alex Hormozi says".

If the user asks what one of them really thinks, say you can only apply their

public frameworks.

Step 0: the idea file

Everything in the founder pack reads founder/idea.md in the user's project. If

it does not exist, write it now from the conversation:


# <business name, or a working name>

- What it is: one sentence.
- Who it is for: the target customer, as specific as the user can make it.
- What it sells, at what price: the core product and its price.
- Where and how: city or online, how customers find it, how it is delivered.
- Budget and constraints: money, time, skills, anything already decided.

If the name, the customer, the product or the price is missing, ask for those (at

most three questions in one message), then write the file. Do not invent a

budget, a market size or a competitor.

Step 1: brief the board

Write founder/board/brief.md: the idea file plus anything else the user said

that a stranger would need. **Sub-agents cannot see this conversation**, so the

brief must stand on its own. Do not add your own opinion of the idea to it.

Step 2: convene

Launch three sub-agents in ONE message (Agent tool, `subagent_type:

general-purpose, one per member), each told: Read founder/board/brief.md and

founder-board's lenses.md (path below), apply ONLY the <lens> lens, and write

your memo to founder/board/<lens>.md. The lens file is lenses.md` in this

skill's folder (${CLAUDE_SKILL_DIR}/lenses.md; if that path is not expanded,

use the base directory Claude Code printed for this skill).

Each memo, in this shape:


# <Lens> lens
Score: <1-10> | Vote: FUND / FUND IF / PASS
## What is strong
## What would kill it (the top 3, most dangerous first)
## The questions I would ask the founder
## If FUND IF: the conditions
View full documentation

Step 3: the chair's summary

Read the three memos (they are short) and write founder/board.md:

1. The vote, e.g. "2 fund if, 1 pass", and the average score.

2. The risks more than one member raised: these go first.

3. Every condition, merged, as a checklist the rest of the pack can tick off

(the CFO, the consumer panel and pricing will test most of them).

4. One paragraph: the strongest version of this business the board can see.

It may differ from what the user pitched; say so plainly.

Keep the members' disagreements. A board that agrees on everything was not doing

its job.

Rules

  • Score the business, not the founder.
  • No made-up facts. If a lens needs a number nobody has yet (market size, cost of

acquiring a customer), name it as an open question and say which skill answers

it (/founder-competitors, /founder-consumer, /founder-cfo).

  • A PASS is a result, not a failure. Say it plainly.

Output

founder/idea.md, founder/board/ (brief and three memos), founder/board.md.

Then say the vote in one line and suggest the next step: /founder-competitors

to see who is already there, or /founder-consumer to put it in front of 100

simulated buyers.

Where the pack goes next


board -> competitors -> consumer -> pricing -> offer -> cfo -> marketing -> brand -> ops -> launch -> plan

Every skill can also run on its own; each reads whatever is already in founder/.

Score breakdown

Trigger
8.0
Rich What+When description: three named lenses, vote vocabulary (fund/fund if/pass), many trigger phrasings ('test my business idea','would this work','pressure-test this','what would a board say'). No explicit When-Not clause.
Structure
8.7
SKILL.md 111 lines with lens details offloaded to lenses.md (84 lines). lenses.md lives at skill root rather than references/; otherwise clean, no redundant files.
Workflow
9.2
Clear 4-step workflow (idea file gate with max-3 questions, standalone brief because sub-agents lack conversation context, one-message sub-agent fan-out with fixed memo shape, chair's synthesis preserving disagreements). Strong guards: never speak as the real people, no made-up facts, missing numbers become open questions routed to sibling skills.
Content
10.0
Very concise imperative writing, concrete memo template, explicit file outputs and pack sequence diagram.
Engineering
10.0
Valid frontmatter with argument-hint. No scripts (none needed). lenses.md path resolution explained for sub-agents; all referenced files exist.
Security
10.0
Capability manifest: reads founder/idea.md and conversation; writes only founder/idea.md, founder/board/ brief+memos, founder/board.md; no network destinations; no credentials; no persistence. Capabilities match declared scope. No scripts, no injection, no secrets.
Multi-agent review skill: three sub-agents apply published frameworks (Hormozi offers, Thiel monopoly, Jobs product) to a business idea, write structured memos, and a chair summary merges votes/risks/conditions. Clean design with good anti-hallucination guards. Minor: lenses.md sits at skill root instead of references/; no explicit When-Not in description.