cus
Skill0 starsChanged 40 days agoMITView on GitHub
Use when the user says "close up shop", "cus", "wrap up", "that's it for today" or types /cus — end-of-session routine that writes the session back into the ~/Notes brain and pushes it.
- Commits and pushes
In this repository3 other files it gives its agents.
- brain-polishSkill
- deskSkill
- wildSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 8
Write today's session back into the brain, then stop.
≈ “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
Close up shop
Write today's session back into the brain, then stop. Don't start new work.
- Session note —
~/Notes/sessions/YYYY-MM-DD-<slug>.mdfrom~/Notes/.brain/session-template.md(frontmatter: date, title, projects, status, cwd). TL;DR, What happened, Decisions, Open threads. Facts only from this session. If a note for today already exists from this session, add to it; never rewrite older session notes. - Project pages — for each project touched: current state, open threads,
updated:date. Learned something about a person → theirpeople/page. Course work → the course's Weekly file (Confused about/Flagged for the examare worth filling). - now.md — true, punchy headline + dek, add to Done, keep ≥5 dated Upcoming items.
- Nudges — add any real promise/deadline left open to
nudges.md. Never re-add astatus: noone. - Build + push —
python3 ~/Notes/.brain/build.py, then in~/Notes:git add -A && git commit -m "<session title>" && git push(Bash needsallowed_domains: ["github.com"]). - Report — 2–3 lines: what was saved, anything left open for tomorrow.
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.

