chiron
Skill1 starsChanged 23 days agoMITView on GitHub
Route advisor requests to Chiron seats, and auto-orchestrate decisions to the right expert(s). Use when the user asks what a named advisor/seat would say ("what would munger say", "ask naval about this"), describes a decision without naming anyone ("should I take this deal", "help me think through this", "I'm stuck on pricing"), wants to be coached through a decision and held to a committed call ("coach me", "walk me through this", "help me decide and keep me honest"), wants to run a question by a bench or council ("run this by my product bench", "convene the council"), wants to see available advisors ("who can I ask"), or wants to add a seat ("distill a seat for X", "add an advisor"), wants to get set up ("onboard me", "get me started"), or wants to distill themselves into a seat ("distill me", "build my seat", "put me on the council"). Covers consult (auto-routing), coach (a guided decision session), ask, council, bench, roster, distill, distill-me, onboard, lint, and log without slash syntax.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- eragonlonelyboy-lab/chirontheir own version, first seen Jul 7, 2026
- gyasis/chirontheir own version, first seen Apr 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- gyasis/chiron★ 2same name
- eragonlonelyboy-lab/chiron★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
When the user is mid-decision but has not asked Chiron for anything, offer to route rather than hijacking the turn.
- Very specific: line 33
Never invent a seat that isn't installed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chiron router
The user invoked Chiron conversationally. Map their intent to the matching command file under ${CLAUDE_PLUGIN_ROOT}/commands/ and follow it exactly. The command files are the source of truth for each flow's contract.
On Claude Code, ${CLAUDE_PLUGIN_ROOT} is the installed plugin directory. ChatGPT and Codex do not set that variable. There, the plugin root is the directory that contains skills/ and scripts/, and every ${CLAUDE_PLUGIN_ROOT} in a command file means that directory. The ask, council, coach, and log skills are the same flows for hosts with no slash commands. They follow these command files and do not carry a second copy of any seat.
Default to orchestration. When the user describes a decision or a situation but does NOT name a specific seat or bench, do not guess or grab the whole roster. Follow commands/consult.md: it decides whether to skip, ask one seat, or convene a council, and picks the right experts. That routing decision is the point of the product.
| Intent sounds like | Follow |
| a decision/situation with no seat named ("should I...", "I'm torn on...", "help me decide...") | commands/consult.md (auto-route) |
| wants to be worked through a decision and held to a committed call ("coach me", "walk me through this", "help me decide and keep me honest") | commands/coach.md (coach loop) |
| "get started", "set me up", "onboard me" (first run) | commands/onboard.md |
| "distill me", "build my seat", "put me on the council" | commands/distill-me.md |
"ask <seat> ...", "what would <seat> say about ..." | commands/ask.md |
"run this by <bench>", "convene ...", "council on ...", "what does my <bench> bench think" | commands/council.md |
| "create/show/edit a bench", "my line-up for X" | commands/bench.md |
| "who can I ask", "show the roster", "which seats do I have" | commands/roster.md |
"distill/add a seat for X", "I want a <person> advisor" | commands/distill.md |
| "check/validate my seats", "lint" | commands/lint.md |
"what did <seat> tell me", "open loops", "past consults" | commands/log.md |
Resolution notes:
- Seat and bench names arrive fuzzy ("munger", "the Munger seat", "my pricing people"). Resolve against
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/registry.py --json --seats-dir ${CLAUDE_PLUGIN_ROOT}/skills --seats-dir ~/.claude/skills --seats-dir ~/.claude/chiron/seats --seats-dir ~/.chiron/seats --seats-dir .claude/skills --seats-dir .chiron/seatsandpython3 ${CLAUDE_PLUGIN_ROOT}/scripts/benches.py --json(project.chiron/benches.yaml, global~/.chiron/benches.yaml, a leftover~/.claude/chiron/benches.yaml, or the bundled examples when the user has none of those). The~/.claude/seat dirs are read only; Chiron writes new seats under~/.chiron/seats(or the directorypython3 ${CLAUDE_PLUGIN_ROOT}/scripts/memory.py seatsprints). Seat wins ties; ask once if genuinely ambiguous. Never write under~/.claude. - Explicit beats inferred: if the user names a seat, honor it (ask); if they say "they/the bench/the council" or name a bench, go to council. Only auto-route (consult) when they leave the choice open.
- Consult vs coach: use
consultwhen they want the decision routed to the right expert(s) and answered in one shot; usecoachwhen they want to be walked through it and driven to a committed call with a next action. If they sound like they want a working session, prefer coach; a one-shot question, consult. - When the user is mid-decision but has not asked Chiron for anything, offer to route rather than hijacking the turn.
- Never invent a seat that isn't installed. Offer
/chiron:distillinstead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.