Skip to content
mcp/skillhub

Agent Skill

Muse Delegate skill

muse-delegateamElnagdy/delegate-skillsskills/muse-delegate/SKILL.md

Delegate a coding task to Muse Code (`muse`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Muse — phrasings like "have Muse do X", "delegate this to Muse", "run it through Muse", or "use Muse to implement/fix/refactor" — or wants to run a queue of coding tasks through Muse while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. It applies only when the user wants that separate `muse exec` implementer run: if you are Muse yourself and the user simply asks you to write the code, do it directly. DO NOT USE for tasks small enough to do inline.

2.5kMIT

always on

157 tokname + description

once used

2,065 tokSKILL.md body

bundled files

51 scripts

repo stars

2.5kGitHub

Install the Muse Delegate skill

Skills CLI (Claude Code, Codex, Cursor and others)

npx skills add https://github.com/amElnagdy/delegate-skills --skill muse-delegate

Claude Code, by hand (all projects)

git clone --depth 1 https://github.com/amElnagdy/delegate-skills.git /tmp/delegate-skills
mkdir -p ~/.claude/skills
cp -R /tmp/delegate-skills/skills/muse-delegate ~/.claude/skills/muse-delegate

For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.

What it costs your context

Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.

WhenWhat loadsCost
Every sessionName and description157 tok
When the agent uses itThe SKILL.md instructions2,065 tok
Only if opened5 bundled files (54 KB)varies

Until it is used, muse-delegate costs about 8.7× less than the median MCP server we measured (1,363 tokens on every turn). Installing all 20 skills from amElnagdy/delegate-skills would load 2,566 tokens of descriptions. Skills vs MCP study

Checks

  • Ships scripts the agent can run. Read them before installing.

Checked 2026-10-22 · method

What's inside

The headings of its SKILL.md. Read the full file on GitHub.

  • Muse Delegate
  • When NOT to use this
  • Read this before the first dispatch: the autonomy model
  • Prerequisites (check once)
  • Choose the implementer model
  • The loop
  • 1. Write the brief
  • 2. Dispatch
  • 3. Wait for completion
  • 4. Review — do not trust the self-report
  • 5. Land it
  • Authorization model
  • References

More skills from amElnagdy/delegate-skills

All skills in this repo
  1. agy-delegateamElnagdy/delegate-skills

    Delegate a coding task to the Google Antigravity CLI (`agy`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use Antigravity to implement/fix/refactor" - or wants to run a queue of coding tasks through agy while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

    2.5k1132 tok idle · 2,362 in use
  2. aider-delegateamElnagdy/delegate-skills

    Delegate a coding task to Aider (`aider`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Aider - phrasings like "have Aider do X", "delegate this to aider", "run it through Aider", or "use Aider to implement/fix/refactor" - or wants to run a queue of coding tasks through Aider while staying the reviewer. This includes asking Aider to drive a local or self-hosted OpenAI-compatible endpoint ("have Aider use my local model", "run Aider against llama.cpp / Ollama / vLLM / LM Studio"), which Aider reaches via `--api-base`. DO NOT USE for local-model or coding requests that do not name Aider, for tasks small enough to do inline, or when the user wants the code written directly without delegating.

    2.5k1190 tok idle · 2,766 in use
  3. claude-delegateamElnagdy/delegate-skills

    Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the `claude` CLI — for example, "have another Claude implement this", "delegate this to Claude Code", or "run this queue through a separate Claude session." Do not trigger merely because the current orchestrator is Claude, and do not use when the user asks the current Claude to implement directly without delegation.

    2.5k1117 tok idle · 2,083 in use
  4. cline-delegateamElnagdy/delegate-skills

    Delegate a coding task to the Cline coding agent CLI (`cline`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Cline - phrasings like "have Cline implement X", "delegate this to cline", "run it through Cline", or "use cline to implement/fix/refactor" - or wants to run a queue of coding tasks through Cline while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

    2.5k1126 tok idle · 1,476 in use
  5. codex-backgroundamElnagdy/delegate-skills

    Keep a Codex orchestrator's delegation to an installed delegate skill pending until its registered relay completes, without model-driven progress polling. Use with a selected implementer delegate skill when Codex is the orchestrator and the delegation should wait in the background; sets up its MCP server on first use.

    2.5k663 tok idle · 725 in use
  6. codex-delegateamElnagdy/delegate-skills

    Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Codex — phrasings like "have Codex do X", "delegate this to Codex", "run it through Codex", or "use Codex to implement/fix/refactor" — or to run a queue of coding tasks through Codex while staying the reviewer. Prefer it over a one-shot Codex forwarder (such as the codex-rescue agent) when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

    2.5k1155 tok idle · 2,557 in use
  7. commandcode-delegateamElnagdy/delegate-skills

    Delegate a coding task to the Command Code CLI (`cmd`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Command Code — phrasings like "have Command Code do X", "delegate this to commandcode", "run it through cmd", or "use Command Code to implement/fix/refactor" — or to run a queue of coding tasks through Command Code while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

    2.5k1123 tok idle · 2,485 in use
  8. copilot-delegateamElnagdy/delegate-skills

    Delegate a coding task to the GitHub Copilot CLI (`copilot`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it through Copilot CLI", or "use copilot to implement/fix/refactor" - or wants to run a queue of coding tasks through Copilot while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

    2.5k1129 tok idle · 1,654 in use