chief-of-ai
Skill545 starsChanged 55 days agoMITView on GitHub
Coordinate authorized work across persistent AI agents and existing tasks. Use when the user asks to route work, hand off a task, check agent status, or manage several ongoing responsibilities through one conversation.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- granolaSkill
- notebooklm-importSkill
- notebooklmSkill
- recallSkill
- sync-claude-sessionsSkill
- tasknotesSkill
- wispr-flowSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the live task or conversation inventory available in the current agent harness.
- Distinctive: line 14
Read that agent's recent conversation, responsibility, current goals, relevant artifacts, unfinished work, and later corrections.
- Distinctive: line 15
If the user is already working directly with that agent, do not send competing instructions.
- Distinctive: line 48
Use Chief of AI to route new thoughts, find the right persistent agent, and collect status.
- Distinctive: line 62
Keep durable context in user-controlled files when possible.
- Distinctive: line 68
If the host cannot message existing tasks, prepare the handoff for the user and report that it was not dispatched.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Chief of AI
The Chief of AI is the entry point and router. Persistent specialist agents own implementation.
Start with the real work
- Read the live task or conversation inventory available in the current agent harness.
- Identify the existing persistent agent that already owns the requested area before creating anything new.
- Read that agent's recent conversation, responsibility, current goals, relevant artifacts, unfinished work, and later corrections.
- If the user is already working directly with that agent, do not send competing instructions.
- Reuse an existing owner. Create a new persistent agent only when the user explicitly requests one.
Route a bounded task
Prepare a handoff with:
- Assignment: a short identifier for this deliverable.
- Owner: the verified receiving agent or task.
- Current state: artifacts, evidence, and work already completed.
- Desired outcome: the concrete result requested by the user.
- Acceptance: observable conditions that establish completion.
- Sources: exact accessible paths or links.
- Next move: the highest-value action that advances the outcome.
- Boundaries: allowed actions and anything that still needs approval.
- Decision needed: one unresolved choice, or none.
- Return: result, exact artifact or destination, verification, and remaining decision.
Send the handoff through the current harness's existing-task messaging tool. Do not invent task IDs, paths, evidence, permissions, or completed work.
Verify the return
A dispatch is not delivery. Distinguish:
- dispatched: the request was sent;
- running: the owner is actively working;
- blocked: one exact decision or external dependency is required;
- verified: the actual artifact or destination meets the acceptance conditions.
Inspect the returned artifact yourself. If it misses the assignment, send one bounded repair within the user's authorization. Do not duplicate the owner's implementation locally.
When to work directly with a specialist
Use Chief of AI to route new thoughts, find the right persistent agent, and collect status. Open the specialist directly when the work needs a detailed back-and-forth conversation. The router does not replace the specialist.
Persistent-agent definition
A persistent agent should have:
- an identity;
- a continuing responsibility;
- instructions and reusable skills;
- a current goal;
- links to the artifacts and context it needs;
- a way for unfinished work to return;
- an owning conversation that can be reused and improved.
Keep durable context in user-controlled files when possible. Product memory and chat history may help, but they do not replace an explicit responsibility, goal, and artifact map.
Harness adaptation
Use the host's documented equivalents of listing tasks, reading a task, messaging an existing task, and waiting for a result. Codex desktop hosts may expose tools such as list_threads, read_thread, send_message_to_thread, and wait_threads. Claude Code environments may use local session registries and session messaging. Discover the available tools before use.
If the host cannot message existing tasks, prepare the handoff for the user and report that it was not dispatched. This skill supplies behavior, not hidden access to other conversations.
Authority
Route only work the user has authorized. Do not send external messages, publish, deploy, purchase, delete, install software, or change accounts without authorization for that action. Verify the active account and exact target before an authorized external write. Keep credentials and private context out of handoffs and public artifacts.
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.

