- name
SKILL.md
Файл навыка остаётся в репозитории издателя.
Вставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add coreyhaines31/makerskills --skill maker-council -a cursor -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add coreyhaines31/makerskills --skill maker-council -a claude-code -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add coreyhaines31/makerskills --skill maker-council -a codex -yВставьте скопированную команду в терминал. Она установит этот SKILL.md в выбранного агента.
npx skills add coreyhaines31/makerskills --skill maker-council -a grok -yОтправьте скопированное сообщение в чат Grok Bot. Бот загрузит этот SKILL.md с GitHub и добавит его к навыкам, общим для всех ваших ботов.
Install this skill: https://github.com/coreyhaines31/makerskills/tree/HEAD/skills/maker-councilОт издателя
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.
Clarify (ask only for what's missing, one message):
project_*.md) and ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/business-brainstorm/portfolio.local.md before asking — the user may already be on file.Then write the brief — under 300 words, the only thing every member reads:
(assumed). Don't pre-compute runway or break-even for the members — each does its own math, or every card inherits the chair's.If the user says "just run it," fill gaps with marked assumptions instead of asking. Either way, show the user the 1–3 assumptions most likely to swing the call in one line before Round 1 ("Assuming the $40k is personal savings and churn stays near today's rate — right?"). Members build on the brief, so an unchecked guess becomes a premise.
Match the session to the stakes. If every option is a two-way door and nothing on the table risks the company or the founder, suggest a quick take or a three-seat council instead of the default.
Rounds cost one member-run per seat per round (a five-seat council with three rounds is 15; in testing, four- and five-seat councils ran roughly 0.7–1.4M tokens). Say which mode ran.
Nine members, chosen so their lenses collide. Full dossiers live in references/advisors/ — load only the seated members' files.
For a council session, seat 3–5:
Quick take skips the rounds: one member, 2–4 paragraphs that apply their signature questions and frameworks to the user's specifics (not generic advice with a name attached), in their voice, ending in a one-line bottom line. Everything below is for council sessions.
You are the chair: you run the room, keep the score, and write the verdict. You never argue a side. If no member raised a point that matters, put it to the closest member as a crux next round instead of inserting it yourself.
references/advisors/ and the config advisors dir (${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/maker-council/advisors/), which holds custom members.brief.md.round-1.md, then add chair notes:
round-2.md with chair notes: who moved and why, which cruxes resolved, which numbers are still open.draft.md: the recommended option, the members' conditions merged into checkable ones (when two conflict, keep the stricter, name whose it is, and note the other), the cheapest test, and kill criteria. Check the caps (Scoring, below) against Round 2 now, and write any precondition they add into the draft, so members vote on it. Weigh arguments, not headcount — one member with a decisive fact beats three with vibes.Use the last round that ran. Every number comes from the cards — the chair computes, never invents.
ruin likely blocks a plain "do it." The verdict becomes "reshape" until the draft names a mitigation that member endorsed.ruin possible, the verdict is "do it with conditions" at most, and the test must pass first.When the topic is specific or the user wants sources, go beyond the dossiers:
deep-research — find what seated members have actually said or written about this topic class (books, shareholder letters, essays, interviews, podcasts). The brief archives per deep-research's own convention.watch-video — pull transcripts from specific talks/interviews the research surfaces./last30days — recent takes when the topic is fast-moving (living members' positions evolve).Save findings per member to research.md in the session folder and point each member at its section, so the cards can cite them ("In the 1997 shareholder letter, Bezos wrote…"). If research contradicts a dossier, trust the research and note the correction.
> Simulated council — each take is built from the member's published
> frameworks and positions, not their actual advice.
## The question before the council
[1–2 sentence restatement + what's at stake]
## Seated: [A], [B], [C] ([mode], [rounds run])
[One line on why this bench, including who's the dissenter]
## The call: [option] — [do it / do it with conditions / reshape / don't do it]
Scores: A 6.8 · B 7.4 · C 3.1 — spread on B: 3. [Any cap applied, and why.]
Your lean was [lean]; the council [backed it / changed it / split] because [one line].
Hinges on: [any `(assumed)` item the call depends on — "if this is wrong, re-run"]
---
### [Member A] — [their lens, 3–5 words]
[Final position from their last card: the call, the 2–3 arguments that
carried it, what they conceded, whether they moved]
**Bottom line:** [their ONE LINE FOR THE FOUNDER, from their last card]
…
---
## Where the council disagrees
1. **[Crux]** — [A] says X because [framework]; [B] says Y because
[framework]. The real trade-off: [tension]. Resolved in debate? [how, or
still open]. What would settle it: [evidence/test].
## Chair's synthesis
[Recommendation fitted to this user's stage and constraints]
- **Conditions:** [the checkable ones from the draft]
- **Cheapest test first:** [what, and the kill criteria]
- **Dissent:** [who, and their strongest argument, unsoftened. If nobody
dissents, say so and give the strongest argument that went unanswered]
- **Tripwire:** [which member's warning to monitor, and the signal — taken
from a card's WHAT WOULD CHANGE MY MIND or conditions, not invented]
- **Next:** [skill handoffs — usually /decide to formalize the call]
Full rounds: [path to the session folder]
Members' sections summarize their cards; never rewrite a member's argument into something they didn't say.
In chat, show the header through "Hinges on," plus the conditions, cheapest test, and dissent — under 200 words — then the path to verdict.md. If conditions must be cut for length, keep the ones the dissent or the kill criteria refer to. The member sections and disagreement map live in the file; show them in chat only when asked. A user who says "just give me the answer" gets exactly that.
Sessions archive to ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/maker-council/archive/ (create if missing). Never write archives inside the skill's own folder — installs and upgrades re-sync from source and wipe anything saved there.
A council session gets a folder, <archive dir>/<YYYY-MM-DD>-<slug>/, filled as the session runs: brief.md, round-1.md, round-2.md, draft.md, round-3.md (if it ran), and verdict.md (the output format above, plus a header noting seated members and mode). Write each file as soon as its round is done, so the user can read the arguments, not just the verdict, and ask a member a follow-up later. A quick take is a single file, <archive dir>/<YYYY-MM-DD>-<slug>.md.
When the verdict is written, append to <archive dir>/INDEX.md (create if missing):
- 2026-07-15 — [<question>](./<folder>/verdict.md) — seated: <members> — **<recommendation in one line>** (spread <n>)
Users can extend the bench ("add my own advisor"). Create a dossier following references/advisor-template.md and save it to ${MAKERSKILLS_CONFIG:-$HOME/.config/makerskills}/maker-council/advisors/<kebab-name>.md — never inside the skill folder (upgrades wipe it). Two grounding standards:
When convening, check the config advisors dir and treat any dossiers there as bench members.
/decide formalizes the call; execution skills do the work.decide — the chair's synthesis usually ends in a fork; /decide formalizes and archives the calldeep-research / watch-video / /last30days — the live research passbusiness-brainstorm — when the question is "should this business exist," run that first; bring the brief to the councilunstuck — when the council agrees the goal is right but the path is blockedmarketing-skills:marketing-council — sibling bench for marketing questionsWhen 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
---name: maker-councildescription: When you want multiple expert perspectives on a founder/operator question — a simulated board of advisors…---# skills/maker-council/SKILL.mdОбзор
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.
FAQ
Скачайте skills/maker-council/SKILL.md у издателя или скопируйте путь и откройте репозиторий. PlugMCP только показывает навык в каталоге и не хранит файл.
Издатель хранит его в https://github.com/coreyhaines31/makerskills.
Claude, Cursor, Codex и Grok Build могут читать SKILL.md, который вы добавляете из репозитория издателя. Grok Bot устанавливает его, когда вы отправляете в чат ссылку на папку навыка на GitHub.