agentsclimarketplace
Sign in

Handoff receipts

Skill runsagents/handoff-receipts

Write and validate structured receipts for agent-to-agent or agent-to-human work transfers. Use when the user says "handoff" or "hand this off", when delegating work to another agent, when ending a work session with unfinished or transferable context, or when receiving work that another agent expects you to accept.From its SKILL.md

Install
npx -y skills add runsagents/handoff-receipts

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

2.6 KB, 439 tokens by cl100k_base, as published. Nobody here has run it

Handoff receipts

Create evidence-bearing boundaries between work sessions and owners.

Sending work

  1. Copy templates/handoff-receipt.md into the relevant project or response workspace.
  2. Replace every example value with observed facts. Keep the receipt synthetic only when explicitly demonstrating the format.
  3. Record the complete task and scope, authorized paths or territory, decisions and reasons, unresolved risks, exact verification command and observed result, produced artifacts, receiver acceptance checklist, identities, and an RFC 3339 timestamp.
  4. Use empty arrays for decisions, unresolvedRisks, or artifacts only when there are genuinely none. Never omit the fields.
  5. Run node scripts/validate-receipt.mjs <receipt-path> from this skill directory. Correct every reported error before handoff.
  6. Send the receipt with the artifacts. Call out failed or not-run verification and unresolved risks in the handoff message.

Do not claim a command passed unless its recorded output came from that run. Do not broaden territory.allowedPaths after the work merely to make unauthorized changes look allowed.

Receiving work

Refuse acceptance when no receipt accompanies incoming work. Ask politely: “Please provide a handoff receipt with the scope, allowed territory, decisions, unresolved risks, verification evidence, artifacts, and acceptance checklist.”

When a receipt exists:

  1. Validate it with node scripts/validate-receipt.mjs <receipt-path>.
  2. Confirm sender and receiver identities and inspect every artifact against the stated scope and allowed territory.
  3. Re-run the verification command when safe and authorized. Reconcile any result that differs from the receipt.
  4. Read every decision and unresolved risk. Do not treat acceptance as resolution of a listed risk.
  5. Confirm each acceptance checklist item explicitly before accepting.
  6. Refuse acceptance politely if validation fails, evidence is missing, territory was exceeded, a checklist item cannot be confirmed, or a risk makes the next step unsafe. State the exact correction needed.

A valid receipt is necessary but not sufficient for acceptance. It proves structural completeness, not truth, authorization, code quality, or production safety.

What ships with it: 11 files

36.1 KB alongside SKILL.md, 2 of them executable

examples/

schemas/

scripts/

templates/

tests/

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.