claude-delegate
Skill0 starsChanged 49 days agoNo licenceView on GitHub
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.
- Commits and pushes
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- ricardodeazambuja/tui-drivertheir own version, first seen Oct 30, 2026
- amElnagdy/delegate-skillsedited, first seen Jul 29, 2026
- fergus/claude-kimi-delegatetheir own version, first seen Apr 30, 2026
- StoicEnso/openclaw-claude-delegatetheir own version, first seen Apr 19, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- amElnagdy/delegate-skills★ 2.6k90% same
Wrote their own version · 3
- ricardodeazambuja/tui-driver★ 1same name
- fergus/claude-kimi-delegate★ 0same name
- StoicEnso/openclaw-claude-delegate★ 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 repository8 other files it gives its agents.
- agy-delegateSkill
- bim-software-devSkill
- codex-delegateSkill
- commandcode-delegateSkill
- copilot-delegateSkill
- delegate-setupSkill
- find-skillsSkill
- karpathy-guidelinesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.