agentsclimarketplace

Handoff

Skill aylee/agent-os/.agents/skills/handoff

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.From its SKILL.md

Install
npx -y skills add aylee/agent-os --skill handoff

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

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.

  1. 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.
  2. Copy the template exactly. Preserve its required frontmatter names: schema_version, handoff_id, workstream_id, base_revision, created_at, created_by_runtime, and target.
  3. Create a uniquely named file under state/handoffs/<workstream-id>/ using UTC time and a handoff-<uuid> ID.
  4. 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 exact base_revision.
  5. 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.
  6. Never mutate the handoff into a receipt. A receiving agent may create a separate consume-handoff receipt.

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/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.