handoff
Skill2 starsChanged 3 months agoMITView on GitHub
Distill the current conversation into a self-contained handoff prompt for a fresh chat. Use when a thread has grown long or is about to be compacted, when switching to a new focused task, or when the user says "hand off", "start a new thread", "carry this over", or "summarize this for a new chat".
191 other projects use a version of this.
Adopted by
Most recently taken up by
- xiaoxiaosrm/dsh-mattpocock-skillstheir own version, first seen Nov 8, 2026
- ethosagent/ethostheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
- glebis/claude-skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use decision-mapping, setup-ts-deep-modules and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
FabienDehopreSkilldecision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
Also in 8 projects that use this
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 42 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 93 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 87 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 51 projects that use this
LesaniSkillwriting-beats
Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.
Also in 54 projects that use this
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- GreyDGL/PentestGPT★ 16ksame name
- ykdojo/claude-code-tips★ 10ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- withcoral/coral★ 4.9ksame name
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
181 more not listed
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 repository16 other files it gives its agents.
- _global/AGENTS.mdAGENTS.md
- adhd-modeSkill
- browserSkill
- code-reviewerSkill
- commitSkill
- context7Skill
- datadogSkill
- discordSkill
- firestoreSkill
- linear-cliSkill
- planworkSkill
- slackSkill
- taskmanSkill
- workflowsSkill
- write-an-adrSkill
- write-prSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
2
Distinctive
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 23
If they don't, ask one short question: "What's the next task for the new chat?"
- Distinctive: line 63
Offer to edit: After producing the block, let the user tweak the goal or scope before they start the new chat.
“Common” is measured: kept by at least 6 in 10 of the 172 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Handoff
Compaction is lossy — it shrinks history without knowing what the next task needs. A handoff is the opposite: it extracts exactly what the next task needs and packages it as a prompt you can paste into a fresh chat that has zero prior context.
When to use
- The current thread is long, slow, or near its context limit.
- You're pivoting to a related but distinct task ("now do this for teams too", "execute phase one", "check the other call sites").
- You want a clean chat that still knows the decisions already made.
Input
The user states the goal for the new thread — what they want to do next. If they don't, ask one short question: "What's the next task for the new chat?"
Process
- Review the conversation so far: what was built or decided, which files were read or modified, what approach was chosen and what was rejected.
- Produce a self-contained prompt for the new thread. It must stand alone — the new chat cannot see this conversation.
- Output it in a fenced code block so the user can copy it verbatim. Do not add preamble like "Here's the prompt" — the block is the deliverable.
Output format
## Context
We've been working on <X>. Key decisions:
- <decision 1>
- <decision 2>
Files involved:
- path/to/file1.ts — <what it is / what changed>
- path/to/file2.ts — <what it is / what changed>
Relevant constraints / gotchas:
- <constraint or gotcha discovered along the way>
## Task
<Clear, specific description of what to do next, based on the user's goal.>Rules
- Self-contained. Include every decision, file path, and constraint the new thread needs. Assume it knows nothing.
- Concise but complete. Summarize; don't transcribe. Drop dead ends unless they explain why an approach was rejected.
- Real paths. List actual file paths that were touched or discussed, with a one-line note on each.
- Lead with the task. The
## Tasksection is the point — make it concrete and actionable, not a vague theme. - Offer to edit. After producing the block, let the user tweak the goal or scope before they start the new chat.
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.