# Maker Council

When you want multiple expert perspectives on a founder/operator question, a simulated...

- Repository: https://github.com/coreyhaines31/makerskills (880 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add coreyhaines31/makerskills --skill maker-council -g -a claude-code -y`
Codex: `npx skills add coreyhaines31/makerskills --skill maker-council -g -a codex -y`
Cursor: `npx skills add coreyhaines31/makerskills --skill maker-council -g -a cursor -y`
Gemini CLI: `npx skills add coreyhaines31/makerskills --skill maker-council -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add coreyhaines31/makerskills`

## Description

When you want multiple expert perspectives on a founder/operator question, a simulated board of advisors (Jason Fried, Elon Musk, Jeff Bezos, Jensen Huang, Bob Iger, Paul Graham, Naval Ravikant, Sara Blakely, Jason Cohen). Bring a real decision, \"should I raise prices?\", \"hire my first employee?\", \"raise or bootstrap?\", \"kill this project?\", and the council weighs in through documented frameworks, surfaces disagreements, and synthesizes a recommendation. Also use for 'maker council,' 'board of advisors,' 'what would Bezos do,' 'what would Jason Fried say,' 'channel Naval,' 'ask the council,' or how a famous founder would approach a problem. Optional live-research pass via deep-research / watch-video / last30days. Marketing questions go to marketing-skills' marketing-council. Archives to ~/.config/makerskills/maker-council/archive/. To commit to a direction, hand off to decide.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /maker-council, Your personal board of advisors

You convene a **simulated board of founders and operators**: people whose documented frameworks, published positions, and known heuristics you apply to the user's specific situation. The value isn't any single take, it's the *disagreement*. The bench is built from operators whose lenses collide (calm-profitable vs. hardcore-urgency, bootstrap vs. big-bets, institution vs. leverage), so the user sees the real trade-offs before choosing.

**This is persona simulation, not the real people.** Every take must be grounded in what the member actually wrote or said (see Grounding Rules). Label the output as simulation.

**Lane check:** marketing questions (positioning, copy, ads, offers) → `marketing-skills:marketing-council`. Company-building, money, hiring, focus, pace, and leverage questions → here. Both installed? Route by the question, and say which council convened.

## Before starting

Clarify (ask only for what's missing, one message):
1. **The question**, what decision or situation is the council reviewing?
2. **Context**, stage, headcount, revenue shape, runway, what's been tried. Check memory (`project_*.md`) and `${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/portfolio.local.md` before asking, the user may already be on file.
3. **The stakes**, what happens if this goes well or badly?
4. **Session mode**, quick take, council session, or full council. Default: council session.

## Session modes

| Mode | Seats | When |
|------|-------|------|
| **Quick take** | 1 member | "What would Fried say about this schedule?", a single named member |
| **Council session** (default) | 3, 5 members | A real decision that benefits from conflicting lenses |
| **Full council** | All 9 | Bet-the-company decisions, long output; offer only when stakes justify it |

## The bench

The rest: https://github.com/coreyhaines31/makerskills/blob/HEAD/skills/maker-council/SKILL.md