agentleFS
OhmsSweetOhmsOhmsSweetOhms/claude-skills/handback/SKILL.md

handback

Skill0 starsChanged 58 days agoNo licenceView on GitHub

Close out work with a state-complete handback — the PRODUCER side of ending a packet, plan hop, thread, fleet round, or standalone work stage. Use this skill whenever work is being closed, wrapped, banked, or handed back — "write the handback", "close out this packet", "close the plan hop", "close the thread", "wrap this stage", "bank the results", "write the findings close", "the packet is done" — and even when the user just says work is finished and asks what's next, since finishing IS the trigger. Every handback is the same three moves (STATE block, narrative, bank it); this skill is the single encoded format that replaces months of drifted closeout convention. Do NOT use for booting a session from a handoff (orchestrator-handoff owns that), and when a stricter contract owns the artifact — the Codex handback JSON (threads skill), the ordered session-wrap protocol (orchestrator-handoff), a fleet script's return schema — follow that contract and apply this skill's STATE discipline inside it.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    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 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.