agentsclimarketplace

Handoff

Skill ahgraber/skills/skills/handoff

Agent skills

Install
npx -y skills add ahgraber/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

  • 5 stars5 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

Use when ongoing work must continue in a new conversation, session, or agent with no shared history. Triggers: 'handoff', 'prepare context for next chat', 'summarize for a new session', 'continue this in another conversation'. Not for same-chat status updates or repository documentation.

SKILL.md

2.3 KB, as published. Nobody here has run it

Handoff

Produce a transfer-ready handoff for in-progress work.

Invocation Notice

  • Inform the user when this skill is being invoked by name: handoff.

Critical Constraints

  • Assume the recipient can only see the handoff output and nothing else.
  • Output one fully filled handoff payload in chat.
  • Do not create a handoff file unless explicitly requested.
  • Do not rely on references like "above" or "earlier in this thread".
  • If information is missing, write Unknown and specify what is needed.

When to Use

  • Handing off work to a new conversation or agent.
  • Resetting context while preserving execution continuity.
  • Transferring partially complete implementation/debugging work.
  • Capturing next actions before ending a session.

When Not to Use

  • Simple same-thread progress updates.
  • Creating long-lived project documentation.
  • Retrospectives not intended for immediate continuation.

Workflow

  1. Extract the objective, success criteria, and current status from available context.
  2. Collect concrete evidence: files touched, commands run, validation status, blockers, and risks.
  3. Capture decisions with rationale so the recipient understands intent and tradeoffs.
  4. Fill every section of assets/handoff-template.md.
  5. Ensure next steps are ordered and step 1 is immediately executable.
  6. Return the completed template in chat for copy/paste.

Output Rules

  • Match the template section headings exactly.
  • Keep statements specific and verifiable; avoid vague summaries.
  • Include validation details (passed, failed, or not run).
  • Include blockers with owner/dependency and concrete impact.

Quality Checklist

  • The goal and definition of done are explicit.
  • Done vs. pending work is unambiguous.
  • Blockers include dependency/owner and impact.
  • Validation status includes what passed, failed, or was skipped.
  • The first next step can be executed immediately.
  • The recipient can proceed without asking for missing context.

References

  • assets/handoff-template.md - canonical output format.

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.