Handoff
A filesystem-first, runtime-neutral operating system for agent-assisted work.
npx -y skills add aylee/agent-os --skill handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create a continuation brief for a real agent, runtime, machine, parallel-lane, or context-window boundary. Use when the user clearly asks to hand work to another agent or make it resumable across a named boundary. Do not infer handoff from casual closeout or use it as a substitute for current workstream state.
SKILL.md
1.7 KB, 307 tokens by cl100k_base, as published. Nobody here has run it
Handoff
The linked WORKSTREAM.md must remain independently resumable. A handoff is optional acceleration for a specific boundary.
- Read
docs/state-protocol.md,library/templates/handoff.md, the canonical workstream, and its referenced artifacts. Reconcile stale facts in the workstream before composing the handoff. - Copy the template exactly. Preserve its required frontmatter names:
schema_version,handoff_id,workstream_id,base_revision,created_at,created_by_runtime, andtarget. - Create a uniquely named file under
state/handoffs/<workstream-id>/using UTC time and ahandoff-<uuid>ID. - Preserve the template's section names and order: Boundary, Base Snapshot, Boundary Delta, Artifact References, Risks and Approvals, Suggested Skills, and Receiver First Action. Base Snapshot must name the workspace-relative workstream path, literal
workstream_id, and exactbase_revision. - Keep Boundary Delta limited to transfer-specific context. Reference durable artifacts instead of copying current truth, open decisions, verification, or the workstream's next action. Exclude transcripts, hidden prompts, credentials, personal integration URLs, hostnames, and absolute paths.
- Never mutate the handoff into a receipt. A receiving agent may create a separate
consume-handoffreceipt.
If there is no real boundary, update the workstream and decline to create handoff theater.
What ships with it: 2 files
561 B alongside SKILL.md
agents/
- agent-os.yaml303 B
- openai.yaml258 B
Gives 0 of the 12 instructions most agent orchestration skills give in 307 tokens
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-07
- Reference existing artifacts by path or URLin 53 of 742, across 25 files
- Run the full test suite after integrating changesin 51 of 742, across 19 files
- Dispatch one agent per independent problem domainin 50 of 742, across 17 files
- Verify fixes do not conflictin 45 of 742, across 13 files
- Include a suggested skills section in the documentin 45 of 742, across 17 files
- Redact sensitive informationin 41 of 742, across 11 files
- Save to the temporary directory of the operating systemin 39 of 742, across 10 files
- Tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
- Spot check agent changes for systematic errorsin 34 of 742, across 7 files
- Write a handoff document summarising the current conversationin 31 of 742, across 6 files
- Assign each agent a specific scopein 23 of 742, across 8 files
- Provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- keep the workstream independently resumable
- read state-protocol and handoff templates
- reconcile stale facts in the workstream
- copy the handoff template exactly
- preserve required template frontmatter names
- create a uniquely named handoff file
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.