Memorywhale
wuisabel-gif/MemWhale
Query and write durable debugging memory recorded by MemoryWhale.
A skill your agent uses when somebody asks for an orchestrator, a lead agent, a coordinator, or somebody to "keep an eye on" the agents working on a project — and when asking about who is minding a…
Install Orchestrator
$ npx skills add SirAllap/agentglass --skill orchestrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SirAllap/agentglass orchestrator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SirAllap/agentglass.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/orchestrator .claude/skills/orchestrator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "orchestrator" agent skill from https://github.com/SirAllap/agentglass/tree/main/skills/orchestrator into .claude/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SirAllap/agentglass/tree/main/skills/orchestratorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SirAllap/agentglass --skill orchestrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SirAllap/agentglass orchestrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SirAllap/agentglass.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/orchestrator .agents/skills/orchestrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orchestrator" agent skill from https://github.com/SirAllap/agentglass/tree/main/skills/orchestrator into .agents/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SirAllap/agentglass --skill orchestrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SirAllap/agentglass orchestrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SirAllap/agentglass.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/orchestrator .cursor/skills/orchestrator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "orchestrator" agent skill from https://github.com/SirAllap/agentglass/tree/main/skills/orchestrator into .cursor/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SirAllap/agentglass.git --path skills/orchestrator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SirAllap/agentglass --skill orchestrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SirAllap/agentglass orchestrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SirAllap/agentglass.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/orchestrator .gemini/skills/orchestrator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "orchestrator" agent skill from https://github.com/SirAllap/agentglass/tree/main/skills/orchestrator into .gemini/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SirAllap/agentglass orchestratorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SirAllap/agentglass --skill orchestrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SirAllap/agentglass.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/orchestrator .github/skills/orchestrator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "orchestrator" agent skill from https://github.com/SirAllap/agentglass/tree/main/skills/orchestrator into .github/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SirAllap/agentglass --skill orchestrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SirAllap/agentglass orchestrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SirAllap/agentglass.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/orchestrator .opencode/skills/orchestrator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "orchestrator" agent skill from https://github.com/SirAllap/agentglass/tree/main/skills/orchestrator into .opencode/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
orchestrator- GitHub stars
- 330
- Token cost
- ~1.2k tokens
- SKILL.md length
- 620 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when somebody asks for an orchestrator, a lead agent, a coordinator, or somebody to "keep an eye on" the agents working on a project — and when asking about who is minding a…
- Works in 3 steps: Read the two files it named. The… → Leave it on speak until its line is… → It is woken when the field changes, not…
- Somebody asks for an orchestrator
- SKILL.md covers Put somebody in the chair, One that is already running, What it may do and Asking it things, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Orchestrator is an agent skill from SirAllap/agentglass. Use when somebody asks for an orchestrator, a lead agent, a coordinator, or somebody to "keep an eye on" the agents working on a project — and when asking about who is minding a project, who is blocked, or what the orchestrator last said. Puts a seat in a project's chair inside agentglass (with its own rules, queue, memory and view) instead of a loose tmux session nobody else can see.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. It works with tmux, SQLite and React. The repository describes itself as: 🛰 Every AI coding agent on your machine, on one screen — live cost, tokens and tool calls across every provider, and a hold on anything dangerous until you say go. From your… The licence is MIT.
When your agent uses it
- Somebody asks for an orchestrator
- Somebody to keep an eye on the agents working on a project — and when asking about who is minding a project
- What the orchestrator last said
Example prompts
- “keep an eye on”
- “/orchestrator”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read the two files it named. The template is generic; the rules that make
- Leave it on speak until its line is worth reading.
- It is woken when the field changes, not on a clock. It does not need a loop
What it can do on your machine
Read from SKILL.md and the folder at commit 7808dc8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Orchestrator loads about 1.2k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 620 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SirAllap/agentglass at commit 7808dc8, republished under its MIT licence (© SirAllap). 620 words, ~1,203 tokens.
Download SKILL.mdSave it as
.claude/skills/orchestrator/SKILL.md (or your agent's skills folder).- name
- orchestrator
- description
- Use when somebody asks for an orchestrator, a lead agent, a coordinator, or somebody to "keep an eye on" the agents working on a project — and when asking about who is minding a project, who is blocked, or what the orchestrator last said. Puts a seat in a project's chair inside agentglass (with its own rules, queue, memory and view) instead of a loose tmux session nobody else can see.
The orchestrator's seat
An orchestrator is an agent whose job is NOT to write code. It knows who is working on what, who is stopped and why, hands work out, and answers for the whole field in one line. In agentglass it is a SEAT: one per project, with its own rules file, its own queue, the project's field in front of it, and a view.
Seating one by hand — a tmux window, a prompt pasted in, a loop — makes an agent nobody else can see and nobody can reproduce. This does it properly.
Put somebody in the chair
agentglass-agent orchestrate --project ~/code/<project>Without --project it uses the current directory. It is idempotent: if that
project already has somebody in its chair, you get that agent back rather than
a second one.
The answer names two files. Both are markdown, both live outside the repository, and both are read fresh every seating:
- the doctrine — the rules the SEAT runs by
- the brief — the rules it hands to every agent it opens
They are seeded from a template the first time and then they are yours. The
answer says doctrineSeeded: true when this call created them, which is your
cue to read them and change what does not match this project.
One that is already running
If a session has been orchestrating a project for hours — with agents reporting to it and a context worth keeping — do NOT seat a new one. It adopts itself from inside its own pane:
agentglass-agent adopt --project ~/code/<project> --powers assignNothing restarts, nothing is re-prompted, and no context is thrown away. What it gains is the app knowing who it is: its line in the view, the queue, the field drawn for it with the last hour of every agent, and being woken when that field changes instead of keeping a clock of its own. Its rules files are seeded if missing so there is something to edit; they are not imposed on it.
Standing down an adopted seat releases the claim. It does not kill the session — that would be throwing away somebody's day because a button said "stand down".
Show full SKILL.md (274 more words)Show less
What it may do
--powers speak (the default), nudge, or assign.
| speak | nudge | assign | |
|---|---|---|---|
| read the field, report | yes | yes | yes |
| prompt an agent already running | no | yes | yes |
| start and stop named agents | no | no | yes |
This is a credential, not a sentence in a prompt: a seat set to speak is
refused by the server if it tries to prompt somebody. Start at speak for a
day. Give it assign when its reports have been true.
No level can push, open a pull request, comment, merge, or reach anything outside the machine.
Asking it things
agentglass-agent say "<one line>" # the seat's own report for this round
agentglass-agent recall "<a question>" # what this person already decided
agentglass-agent claim <task-id> --to <agent>
agentglass-agent finish <task-id> "<what came of it>"recall answers out of the precedent bank, and says so plainly when it has
nothing rather than inventing a precedent.
Opening agents
Through the app, never with a bare tmux new-window "cli ...": a CLI that
exits 0 closes that tab and takes its output with it.
agentglass-agent start <name> --cwd <checkout> --yolo # an agent you will prompt
agentglass-agent start <name> --cwd <checkout> --kind <cli> --keep -- <flags>
# a one-shot whose answer you read after it exits
agentglass-agent read <name> # its answer, while the kept tab is there (a day)
agentglass-agent stop <name> # close the kept tab once it is readThe queue
Work is added from the Orchestrator view, and every item carries what would prove it done — a test, a file, an output. An item with no stated proof is allowed and drawn as missing, because a made-up proof is worse than an admitted absence. An item that has beaten two agents stops being handed out and is marked as needing a person.
What to tell somebody who just made one
- Read the two files it named. The template is generic; the rules that make an orchestrator good are the ones about THIS project.
- Leave it on
speakuntil its line is worth reading. - It is woken when the field changes, not on a clock. It does not need a loop and should not be given one.
© SirAllap, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/orchestrator of SirAllap/agentglass.
Open the folder on GitHubat commit 7808dc8
Compare with similar skills
Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Orchestrator this skillSirAllap/agentglass | 330 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Memorywhalewuisabel-gif/MemWhale | 154 | — | ~765 | Automated safety check: Pass | MIT | |
| Retinuejklthinking/retinue | 115 | — | ~279 | Automated safety check: Pass | MIT | |
| Memorywhale Evidencewuisabel-gif/MemWhale | 154 | — | ~459 | Automated safety check: Pass | MIT | |
| Brainstormbkywksj/knowledge-base | 330 | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Memorywhale Debuggingwuisabel-gif/MemWhale | 154 | — | ~370 | Automated safety check: Pass | MIT |
Similar skills
Retinue
jklthinking/retinue
Coordinate work through a local Retinue workspace using its MCP tools.
Memorywhale Evidence
wuisabel-gif/MemWhale
Use MemoryWhale debugging evidence when the user requests recall or a recurring failure may have relevant recorded history.
Brainstorm
bkywksj/knowledge-base
当需要探索方案、头脑风暴、创意思维时自动使用此 Skill. An agent skill from bkywksj/knowledge-base.
Memorywhale Debugging
wuisabel-gif/MemWhale
MemoryWhale debugging; compiler failures; terminal diagnostics.
OpenRig Upgrade Procedure
mvschwarz/openrig
Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.
More from SirAllap/agentglass
Browser Use
SirAllap/agentglass
Drive agentglass's built-in browser — the one already signed in to the sites this project uses.
Related
Categories
Questions about Orchestrator
What does Orchestrator do?
A skill your agent uses when somebody asks for an orchestrator, a lead agent, a coordinator, or somebody to "keep an eye on" the agents working on a project — and when asking about who is minding a…. Orchestrator is an agent skill from SirAllap/agentglass. Use when somebody asks for an orchestrator, a lead agent, a coordinator, or somebody to "keep an eye on" the agents working on a project — and when asking about who is minding a project, who is blocked, or what the orchestrator last said.
When should I use Orchestrator?
Orchestrator fits situations like: somebody asks for an orchestrator; somebody to keep an eye on the agents working on a project — and when asking about who is minding a project; what the orchestrator last said.
How do I install Orchestrator in Claude Code?
Run `npx skills add SirAllap/agentglass --skill orchestrator -a claude-code`. Or copy the skill folder (skills/orchestrator in SirAllap/agentglass) into .claude/skills/orchestrator in your project. Claude Code loads it when a task matches its description.
How do I install Orchestrator in Codex?
Run `npx skills add SirAllap/agentglass --skill orchestrator -a codex`. Or copy the skill folder (skills/orchestrator in SirAllap/agentglass) into .agents/skills/orchestrator in your project. Codex loads it when a task matches its description.
Can I use Orchestrator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SirAllap/agentglass --skill orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestrator, .gemini/skills/orchestrator, .github/skills/orchestrator and .opencode/skills/orchestrator in your project.
What does Orchestrator need to run?
SKILL.md names no scripts, command-line tools or credentials: Orchestrator is instructions for the agent only.
Does Orchestrator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Orchestrator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Orchestrator use?
Orchestrator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Orchestrator use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Orchestrator?
Skills that share tags, products or a category with Orchestrator: Memorywhale (wuisabel-gif/MemWhale, 154 stars), Retinue (jklthinking/retinue, 115 stars), Memorywhale Evidence (wuisabel-gif/MemWhale, 154 stars) and Brainstorm (bkywksj/knowledge-base, 330 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orchestrator?
SirAllap (a GitHub user) maintains it in SirAllap/agentglass, which has 330 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.
Source: SirAllap/agentglass on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.