Handoff
🤖 Curated agent skills for AI agents — one coherent engineering loop that compounds: grill → spec → implement → review → commit → learn. Adopt it or fork it!
npx -y skills add toverux/grimoire --skill handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 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
Compact the conversation into a handoff document a fresh session can resume from.
SKILL.md
1.2 KB, as published. Nobody here has run it
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it to the temporary directory of the user's OS — not the current workspace.
A handoff is compaction for resuming work, never a substitute for a spec: decisions that should outlive the session belong in docs/specs/<feature>.md — write them there first, then reference the spec.
- Include a "suggested skills" section naming the skills the next session should invoke.
- Reference artifacts already captured elsewhere (specs, plans, ADRs, commits, diffs) by path or URL rather than duplicating their content.
- Redact sensitive information: API keys, passwords, personally identifiable information.
- If the user passed arguments, treat them as what the next session will focus on and tailor the document accordingly.
End by reporting the document's path so the user can point the fresh session at it.
Gives 6 of the 12 instructions most agent orchestration skills give
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-06
- run the full test suite after integrating changesin 53 of 742, across 20 files
- reference existing artifacts by path or URLhere, and in 52 of 742, across 22 files
- dispatch one agent per independent problem domainin 50 of 742, across 17 files
- verify fixes do not conflictin 45 of 742, across 13 files
- include a suggested skills section in the documenthere, and in 45 of 742, across 15 files
- redact sensitive informationhere, and in 41 of 742, across 11 files
- save to the temporary directory of the operating systemhere, and in 39 of 742, across 9 files
- tailor the document to user-provided focus argumentshere, and in 39 of 742, across 9 files
- spot check agent changes for systematic errorsin 34 of 742, across 7 files
- write a handoff document summarising the current conversationhere, and in 31 of 742, across 6 files
- assign each agent a specific scopein 23 of 742, across 8 files
- provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- write durable decisions to the spec first
- report the document path to the user
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.