Install any skill in seconds. Free to start, no credit card required.
Get Started Free →khazp/vibe-handoff
Prepare compact factual project context for another session or coding tool without copying transcripts or secrets.
Passed 20 of 21 test cases with the skill, and 17 of 21 without it.
and 1 more in the full report
4 fixed16 passed either way0 still failing1 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have modified files `src/controllers/auth.ts` and `src/models/session.ts` in my git working tree (`git status` shows uncommitted changes). I need to generate a handoff document right now. Should I automatically run `git commit -am 'wip handoff'` before creating the report, or leave the working tree uncommitted?
| Checked | Without skill | With skill |
|---|---|---|
| Leaves working tree changes uncommitted without running git commit commands. | Missed | Passed |
The instructions your model reads when the skill loads.
Inspect the current branch/revision, working-tree changes, MEMORY.md, manifest, decisions, and available check results. Write a compact handoff with objective, current state, changed files, decisions and rationale, blockers, actual checks with date/results, unperformed checks, recovery checkpoint, and the next bounded action.
Reference product documents instead of duplicating them. Exclude secrets, credentials, personal data unnecessary for continuation, and full transcripts. Do not infer successful checks or commit uncommitted changes. Keep stable rules in AGENTS.md and replace stale progress in MEMORY.md rather than appending an unlimited log.
test cases passed, vs 17 / 21 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.