handback
Skill4 starsChanged 2 months agoMITView on GitHub
Return your work to the parent agent that spawned you. Use when you are a child session that has finished (or reached a checkpoint on) a side-quest and the operator wants the findings returned to the originating session.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- OhmsSweetOhms/claude-skillstheir own version, first seen Nov 16, 2026
- broomva/skillstheir own version, first seen Jun 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- broomva/skills★ 4same name
- OhmsSweetOhms/claude-skills★ 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-voiceSkill
- babysitSkill
- changelogSkill
- commitSkill
- desert-modeSkill
- dispatchSkill
- handoffSkill
- mailboxSkill
- open-prSkill
- quickchartSkill
- reviewSkill
- session-usageSkill
- spawnSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Run the mailbox reply flow against $zero — compose the return body per the mailbox compose rules and stream it in.
- Very specific: line 25
If there is no spawn: message-zero you were not created with a return channel, so there is no parent — use dispatch to send to a named peer …
≈ “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
The mailbox reply flow with the recipient fixed to your parent — the from
of your message-zero, the bootstrap handoff you drained on launch.
Find your message-zero — the message whose
subjectbeginsspawn:, in yourarchive/(orinbox/if still unread):zero="$(grep -rlE '^subject: spawn:' "$(mb_dir "$(mb_resolve_self)")"/{archive,inbox} 2>/dev/null | head -1)"- Run the mailbox
replyflow against$zero— compose the return body per the mailboxcomposerules and stream it in. Confirm to the operator what was sent and to whom (mb_whoisfor the parent's friendly name).
If there is no spawn: message-zero you were not created with a return channel, so
there is no parent — use dispatch to send to a named peer instead.
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.

