aio-handoff
Skill0 starsChanged 32 days agoMITView on GitHub
Save a concise, source-anchored backend execution handoff that another session can safely resume.
In this repository54 other files it gives its agents.
- agent-workflowsSkill
- aio-agentsSkill
- aio-algorithmsSkill
- aio-apiSkill
- aio-architectureSkill
- aio-autoplanSkill
- aio-benchmarkSkill
- aio-brainstormSkill
- aio-canarySkill
- aio-checkpointSkill
- aio-ciSkill
- aio-commitSkill
- aio-compoundSkill
- aio-dataSkill
- aio-debugSkill
- aio-devex-reviewSkill
- aio-doc-reviewSkill
- aio-explainSkill
- aio-feedbackSkill
- aio-ideateSkill
- aio-observeSkill
- aio-optimizeSkill
- aio-pipelinesSkill
- aio-plan-reviewSkill
- aio-planSkill
- aio-proofSkill
- aio-prototypeSkill
- aio-qa-onlySkill
- aio-qaSkill
- aio-releaseSkill
- aio-resumeSkill
- aio-reviewSkill
- aio-securitySkill
- aio-shipSkill
- aio-simplifySkill
- aio-specSkill
- aio-tddSkill
- aio-test-auditSkill
- aio-testSkill
- aio-verifySkill
- aio-workSkill
- aio-worktreeSkill
- all-in-oneSkill
- apple-appstore-reviewerSkill
- backend-algorithmsSkill
- backend-debugSkill
- backend-pipelinesSkill
- backend-planSkill
- backend-reviewSkill
- backend-verifySkill
- complete-destructionSkill
- launch-readinessSkill
- play-policy-insightsSkill
- reverse-engineer-anythingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read current files and ledger.
- Distinctive: line 15
Write in the project's artifact location and link it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
AIO Handoff
Save a concise, source-anchored backend execution handoff that another session can safely resume.
Protocol
- Read current files and ledger; record exact repository/branch/revision, accepted plan/source digests, requested destination and settled decisions.
- List completed/in-progress/blocked U and checkpoint IDs with actual artifacts, commands/results, review findings and external status. Preserve unknowns and user changes.
- Describe the next concrete action and the evidence needed to accept it, including pending async jobs, credentials/access and unresolved decisions. Do not dump the entire conversation.
- Write in the project's artifact location and link it. Avoid secrets and machine-only paths inside portable artifacts; use absolute clickable paths only in the user handoff.
Return and handoff
A durable handoff packet, truthful current state and next action; no fabricated completion or automatic message to another chat.
In a pipeline, use the stage contract and return to the integrating controller. Run only this specialist's owned scope; preserve the user's accepted decisions and existing authorization.
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.