Session handoff
Practical bilingual skills that make AI coding agents more disciplined, testable, and useful in real engineering work.
npx -y skills add Rookage/agent-discipline --skill session-handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
Use when preparing a handoff for another session or agent, summarizing current progress, preserving context, avoiding repeated questions, or ending a long task. Creates a concise handoff document with goals, state, completed work, decisions, next steps, and risks.
SKILL.md
1.0 KB, as published. Nobody here has run it
Session Handoff
中文核心：让下个会话不用从头猜。
Where To Write
Default to outputs/handoff-YYYY-MM-DD-HHMM.md in the current workspace unless the user specifies another path.
Include
- Current objective
- Completed work
- Current state
- Important decisions
- Next actions
- Risks and gaps
- Suggested skills for the next session
Rules
- Redact secrets, tokens, passwords, cookies, and private credentials.
- Reference files and commits instead of copying large content.
- Preserve exact commands only when they matter.
- Keep it concise enough for a fresh agent to use immediately.
Output
Return the handoff file path and the most important next step.
Gives 0 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 URLin 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 documentin 45 of 742, across 15 files
- redact sensitive informationin 41 of 742, across 11 files
- save to the temporary directory of the operating systemin 39 of 742, across 9 files
- tailor the document to user-provided focus argumentsin 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 conversationin 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 to default handoff path unless specified
- include completed work
- include risks and gaps
- redact secrets tokens passwords cookies private credentials
- reference files and commits instead of copying content
- preserve exact commands only when they matter
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.