save-session
Skill0 starsChanged 47 days agoMITView on GitHub
Save what was done in this session to the shared agent memory (log entry + project page update) so any other agent or harness can pick it up later. Use when the user says "save session", "log this session" or "save to memory", or at the end of significant work.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- jemshit/save-sessiontheir own version, first seen Nov 8, 2026
- kriscard/Skillstheir own version, first seen Nov 1, 2026
- abhayla/claude-best-practicestheir own version, first seen Nov 1, 2026
- artificialbeingz/abz-karpathy-llm-wikitheir own version, first seen Oct 20, 2026
- Sagargupta16/agent-braintheir own version, first seen Oct 13, 2026
Used with
Projects with it also use status and ship.
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.
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- faizkhairi/claude-code-blueprint★ 73same name
- jemshit/save-session★ 60same name
- jiten-singh-shahi/salesforce-claude-code★ 15same name
- kriscard/Skills★ 15same name
- abhayla/claude-best-practices★ 9same name
- ingpoc/SKILLS★ 9same name
- david-vrba/claude-power-skills★ 4same name
- hydra-db/hydradb-claude-code★ 4same name
- Erionis/Jarvis-Lite★ 3same name
- Sagargupta16/agent-brain★ 2same name
9 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- memory-boostSkill
- restore-sessionSkill
- retroSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
If the session produced stable knowledge (how to run the project, an architecture fact, a gotcha that will bite again), edit …
- Very specific: line 15
If a decision was made, create wiki/decisions/<slug>.md with frontmatter status: current and review_by: <date>.
- Very specific: line 17
If you used checkpoints, close yours: memory_checkpoint(..., status="done").
- Distinctive: line 18
If the memory home is a git repository, commit only if the user asked you to.
“Common” is measured: kept by at least 6 in 10 of the 18 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
save-session
- Identify the project slug (the directory name, or ask if unclear).
- Summarise the session: one-line
action, onedetailsentence with the key result, andpendingif something is left to do. Facts only; no narrative. - Call
memory_save(project, action, detail, pending, agent="<your harness name>"). - If the session produced stable knowledge (how to run the project, an architecture
fact, a gotcha that will bite again), edit
wiki/projects/<project>.mddirectly and add it under the right##section. Do not copy the log into the page. - If a decision was made, create
wiki/decisions/<slug>.mdwith frontmatterstatus: currentandreview_by: <date>; mark the decision it replacesstatus: superseded. - If you used checkpoints, close yours:
memory_checkpoint(..., status="done"). - If the memory home is a git repository, commit only if the user asked you to.
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.