resume-work
Skill1 starsChanged 2 months agoMITView on GitHub
Reorient at the start of a session. Use when the user says "resume",
6 other projects use a version of this.
Adopted by
Most recently taken up by
- 0xdeafcafe/skillstheir own version, first seen Nov 8, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- marinvch/Cortextheir own version, first seen Nov 1, 2026
- nexus-a1/claude-skillstheir own version, first seen Oct 17, 2026
- bendyworks/claude-skillstheir own version, first seen Oct 13, 2026
- DanielOnPurpose/danielonpurpose-skillstheir own version, first seen Jul 27, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- buildomator/buildomator★ 102same name
- bendyworks/claude-skills★ 1same name
- marinvch/Cortex★ 1same name
- nexus-a1/claude-skills★ 1same name
- 0xdeafcafe/skills★ 0same name
- DanielOnPurpose/danielonpurpose-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 repository2 other files it gives its agents.
- ollama-qwen-setupSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read HANDOFF.md at repo root if it exists.
- Distinctive: line 20
Run git log --oneline -10 and git status to confirm the repo matches the note.
- Distinctive: line 21
If they disagree, trust the repo and say exactly what differs.
“Common” is measured: kept by at least 6 in 10 of the 6 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
Resume work
- Read
HANDOFF.mdat repo root if it exists; summarize it in 3-4 lines. - Surface rule changes: report the "standing rules / skills updated"
section from HANDOFF.md, one line each (skip silently if the section
does not exist). Cross-check for changes made outside a session:
run
git log --oneline --since="<date from HANDOFF.md>" -- CLAUDE.md .claude/for repo-tracked instruction files, and check whether any file under ~/.claude/ (CLAUDE.md, skills/) was modified after the handoff date. If something changed that HANDOFF.md does not mention, flag it explicitly. Confirm the surfaced rules are in effect for this session before proposing next steps. - Run
git log --oneline -10andgit statusto confirm the repo matches the note. - If they disagree, trust the repo and say exactly what differs.
- State the next 1-3 steps from the handoff and start the first one if it is unambiguous; otherwise ask which to start.
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.

