handoff

Installation
SKILL.md

Handoff

Turn what matters about the current session into a short document a fresh agent can read in under a minute and keep working from — no replaying the conversation. A fresh agent handed the raw transcript wastes budget re-deriving what matters and can't tell a settled decision from a passing idea, or a live approach from an abandoned one. The handoff is the signal with the noise removed. Run it deliberately (hence no auto-invocation) — when wrapping up, switching sessions, or nearing a context limit.

How to write it

Work from the actual conversation. Pull out the through-line — what we set out to do, where we got to, what's next — and:

  • Reference, don't restate. If a spec, PR, issue, commit, or doc exists, point to it by path/URL and say what it is; don't paste it (that just creates a second copy that drifts). The thing worth capturing that isn't already written down is the reasoning behind decisions.
  • Capture dead ends. The biggest waste in a fresh session is confidently repeating a failed approach. Record what was tried and why it didn't work.
  • Tailor to the next session's purpose (the user's argument). Let it steer emphasis, especially Next steps. No argument → assume it continues the current work.
  • Redact secrets and personal data. These docs get pasted around and sometimes committed. Reference by name ("the Stripe key in .env"), never by value.
  • Keep it tight. Drop any section with nothing real in it; a few lines is a complete handoff for a small session. Don't pad to fill the template.

Document structure

Drop any section that doesn't apply:

Installs
7
Repository
lelborn/skills
First Seen
Jul 21, 2026