handoff-note
Skill0 starsChanged 3 months agoMITView on GitHub
Summarize active work into a concise continuation handoff. Use when the user asks to summarize progress, create a handoff note, compress context, prepare for another agent/thread/session, remove failed paths, or keep only what is needed to continue.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nadavnaveh/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nadavnaveh/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- compositionSkill
- debug-and-fixSkill
- explain-diffSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Remove repetitions, abandoned hypotheses, failed paths, and incidental exploration.
- Distinctive: line 26
Prefer bullets over prose.
- Distinctive: line 28
Do not include praise, narrative recap, or irrelevant chronology.
- Distinctive: line 29
Keep it short enough to paste into a new thread.
- Distinctive: line 33
Use this structure unless the user requests another format:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Handoff Note
Output
Produce a tight handoff note that lets another agent continue the work without rereading the full thread.
Include only:
- Current goal or request
- Files, modules, commands, branches, or artifacts that matter
- Decisions already made
- Changes completed
- Current state of verification
- Remaining work, ordered by next action
- Blockers or open questions only if they affect continuation
Rules
- Remove repetitions, abandoned hypotheses, failed paths, and incidental exploration.
- Preserve exact paths, identifiers, command names, error messages, and decisions when useful.
- Prefer bullets over prose.
- Mark uncertainty explicitly instead of inventing continuity.
- Do not include praise, narrative recap, or irrelevant chronology.
- Keep it short enough to paste into a new thread.
Shape
Use this structure unless the user requests another format:
Goal:
- ...
Relevant context:
- ...
Done:
- ...
Verified:
- ...
Next:
- ...
Open:
- ...Omit empty sections.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.