Write self handoff
Write a self-handoff note to disk so post-compact Claude can pick up where pre-compact Claude left off. Use right before the user runs /compact, when context is getting long, or whenever you'd otherwise lose session-specific state (job IDs, exact numbers, ruled-out hypotheses, file paths, things you got wrong). Pair with read-self-handoff after the user compacts.From its SKILL.md
npx -y skills add phnazari/claude-whip --skill write-self-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
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 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.
SKILL.md
1.0 KB, as published. Nobody here has run it
Write a self-handoff before /compact
/compact summarises the conversation and inevitably loses session-specific detail. This skill
writes that detail to disk so post-compact you can read it back via read-self-handoff.
Flow
- List
docs/self_handoff/(create it if it doesn't exist). Pick the next filename:docs/self_handoff/YYYY-MM-DD.md, orYYYY-MM-DD-1.md,-2.md, … if today already has files. - Write a single markdown file that includes everything that should not be forgotten at /compact. Use whatever structure fits. Lead with what's most load-bearing for resuming work.