fresh-start
Skill127 starsChanged 5 months agoMITView on GitHub
Continue in a new chat without losing anything — writes a compact handoff to paste into a fresh conversation. Use whenever the user wants to move to a new chat or conversation, hits usage limits, says replies got slow or Claude forgets earlier details, or the conversation has grown long.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- AbdouMoumen/claude-skills-plugintheir own version, first seen Nov 1, 2026
- zach2940/claude-skillstheir own version, first seen Oct 20, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- AbdouMoumen/claude-skills-plugin★ 1same name
- zach2940/claude-skills★ 0same 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 repository5 other files it gives its agents.
- ccoSkill
- doc-digestSkill
- project-contextSkill
- sharpen-promptSkill
- token-checkSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 9
Every message re-sends the whole conversation, so a long one uses up limits fast and recalls its early details worse.
- Distinctive: line 23
Write it in the user's language, under 300 words, inside one code block so it copies cleanly:
- Distinctive: line 43
Cowork: start a new task with the handoff as its first message.
- Distinctive: line 48
Never paste whole files, logs or the transcript into the handoff.
≈ “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
Fresh start
Every message re-sends the whole conversation, so a long one uses up limits fast and recalls its early details worse. A new conversation that starts from a short handoff costs a fraction and stays sharp.
When to offer it
- The user asks to start over, hits a limit, or says replies got slow or forgetful.
- The conversation is clearly long: many long turns, large pasted files or documents. Offer it once, in one sentence, at a natural break. Don't interrupt a short conversation or a task that is nearly done.
The handoff
Write it in the user's language, under 300 words, inside one code block so it copies cleanly:
- Goal — one line.
- Decisions so far — bullets, each with its reason in a few words.
- Current state — what exists now: files, drafts, versions, results. Quote only short snippets that the next step needs; name everything else.
- Next step — the very next thing to do, then any open questions.
- Must not be lost — names, numbers, constraints, preferences, things that were tried and failed.
Then give the saving in one line, as an estimate: "This conversation is about 60K tokens; the handoff is about 500, so each message in the new chat re-sends under 1% of what it does here." Then tell the user: open a new conversation, paste the block, and continue.
On each surface
- claude.ai chat: a new chat with the pasted handoff. In a Project, the project's files stay available, so the handoff can just name them.
- Cowork: start a new task with the handoff as its first message.
- Claude Code:
/compactkeeps working in place and is usually enough. For a clean break,/clearand paste the handoff./cco task patchkeeps structured task state across/compactautomatically.
Never paste whole files, logs or the transcript into the handoff.
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.

