Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/create-handoff
Write a handoff file at .turbo/handoff/<YYYY-MM-DD>-<slug>.md capturing current session state — task, status, open decisions, in-flight changes, next step — so a fresh session can continue without re-deriving context.
Passed 8 of 18 test cases with the skill, and 9 of 18 without it.
and 1 more in the full report
3 fixed7 passed either way8 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
After successfully writing a handoff file that addresses an entry listed in `.turbo/improvements.md`, what cleanup steps should be taken regarding the backlog tracker?
| Checked | Without skill | With skill |
|---|---|---|
| removes the matched backlog entry after writing the handoff file | Missed | Passed |
| deletes .turbo/improvements.md when no entries remain in it | Missed | Passed |
The instructions your model reads when the skill loads.
Write a session handoff file at .turbo/handoff/<YYYY-MM-DD>-<slug>.md so a fresh session can pick up where this one left off.
Get today's date: date +%Y-%m-%d.
Pick a slug for the current task:
If the work is anchored to an existing plan at .turbo/plans/<slug>.md, reuse that plan's slug verbatim.
The user may pass an explicit slug or output path; honor it.
The target path is .turbo/handoff/<YYYY-MM-DD>-<slug>.md. A generated slug takes -2, -3, and so on until the path is free. When the user supplied the slug or path and it already exists, use request_user_input to offer overwrite, a numeric suffix, or a different slug.
When an open decision will outlive the rest of the session's state, still unresolved while the work around it is finished, give it its own handoff. Everything else stays in a single file. Slug the split handoff for that decision rather than appending a collision suffix, and write it to stand alone.
State the chosen path before continuing.
Run git status --short to see uncommitted changes in the working tree.
Survey the conversation context for:
test cases passed, vs 9 / 18 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.