Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fbarrento/handoff
Compact the current conversation into a handoff document for another agent to pick up.
Passed 13 of 19 test cases with the skill, and 3 of 19 without it.
and 20 more in the full report
15 fixed0 passed either way4 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just finished debugging the Redis cache connection issue in our Node.js microservice. Write a transition doc for the next agent and save it inside `docs/handoff_redis.md` within this workspace.
| Checked | Without skill | With skill |
|---|---|---|
| The summary document is saved in the OS temporary directory rather than `docs/handoff_redis.md`. | Missed | Passed |
| The output includes a section recommending skills for the successor agent. | Missed | Passed |
The instructions your model reads when the skill loads.
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS - not the current workspace.
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
test cases passed, vs 3 / 19 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.