agentsclimarketplace

Handoff

Skill sainzs/santiagosainz-skills/skills/core/handoff

Auditable, portable agent skills that turn open-source maintenance - review, debugging, verification, handoff - into repeatable workflows for Codex, OpenCode, and Pi

Install
npx -y skills add sainzs/santiagosainz-skills --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.

What its author says it does

Copied from the file, not written here

Write a durable engineering handoff for ongoing agent work: changed files, current goal, evidence, risks, blocked items, and restart prompt. Use before pausing, compacting context, switching tools, ending a long session, or using work-handoff.

SKILL.md

1.5 KB, as published. Nobody here has run it

handoff

Leave the next agent with enough truth to continue without archaeology.

Unix/Pi Contract

  • Do one job: serialize task state into a restartable text artifact.
  • Consume git status, diffs, commands, risks, and user intent; emit a concise handoff.
  • Treat files as memory and conversation as lossy.
  • Do not fabricate timings, test results, metadata, or authorship.
  • Keep the restart prompt executable.

Use

Use when pausing, switching from Codex to OpenCode or back, preparing a SITREP, ending a long task, or preserving context before compaction.

Gather

Inspect:

  1. Current working directory and branch.
  2. git status --short and relevant diff summary.
  3. Commands run and their outcomes.
  4. Files changed by this task.
  5. Known failures, blockers, and assumptions.
  6. User intent that must survive the handoff.

Output

Write or return:

  1. Goal.
  2. Current state.
  3. Changed files.
  4. Evidence.
  5. Risks and blockers.
  6. Next steps.
  7. Restart prompt.

Quality Bar

  • Distinguish user changes from agent changes when possible.
  • Do not claim verification that did not run.
  • Include exact commands for the next proof.
  • Keep it concise enough to paste into a fresh session.

Keep looking

Skills are one crate of 328,083. 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.