session-memory
Skill0 starsChanged 3 months agoMITView on GitHub
Save what happened this session and restore context at the start of the next one — the "second brain" that survives context resets. Use at session end ("save session", "wrap up") and session start ("where were we", "what's the status").
12 other projects use a version of this.
Adopted by
Most recently taken up by
- GeekFamilyCorp/TricorderKittheir own version, first seen Nov 8, 2026
- apappascs/claude-code-sessionstheir own version, first seen Nov 1, 2026
- alexeyban/EKOStheir own version, first seen Nov 1, 2026
- InanisV/my-claude-skillstheir own version, first seen Aug 22, 2026
- Caelumca/claude-codex-skeletontheir own version, first seen Aug 18, 2026
- moriwo-dev-ai/amateras-registrytheir own version, first seen Jul 26, 2026
Used with
Projects with it also use skill-creator.
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.
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 4 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- oaustegard/claude-skills★ 158same name
- GeekFamilyCorp/TricorderKit★ 32same name
- alexeyban/EKOS★ 26same name
- DangQuangSE/team-development-skills★ 19same name
- lukasreese/claude-skills-starter-kit★ 3same name
- apappascs/claude-code-sessions★ 2same name
- InanisV/my-claude-skills★ 1same name
- Caelumca/claude-codex-skeleton★ 0same name
- ieteerapat/ClaudeSkills1.0★ 0same name
- Mesteriis/Engineering-Bible-AI★ 0same name
2 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 repository6 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- deploySkill
- morning-briefingSkill
- new-projectSkill
- server-checkSkill
- telegram-sendSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
5
Distinctive
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 31
When the user says "save session" / "wrap up" — or when a long session is clearly winding down, offer it:
- Distinctive: line 34
Update Next — overwrite, don't append.
- Distinctive: line 35
Add unresolved problems to Open Bugs
- Distinctive: line 40
When the user names a project or asks "where were we":
- Distinctive: line 50
Never store secrets in memory files
“Common” is measured: kept by at least 6 in 10 of the 11 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
Session Memory
An AI session forgets everything when it ends. Your JARVIS doesn't — because every session writes its ending down and reads it back at the start of the next one.
Storage
Plain markdown, one file per project: ~/.jarvis/memory/<project>.md
# project-name
## Next
The single most important next action. Future-you starts here.
## Sessions
### YYYY-MM-DD
- what was done (2-5 bullets, specifics: commits, files, decisions)
- what broke and how it was fixed
## Open Bugs
- bug — where it lives, what triggers itSave (session end)
When the user says "save session" / "wrap up" — or when a long session is clearly winding down, offer it:
- Summarize the session in 2-5 bullets — commits made, features shipped, bugs fixed
- Update Next — overwrite, don't append; it's a pointer, not a log
- Add unresolved problems to Open Bugs
- Prepend the dated entry under Sessions (newest first)
Restore (session start)
When the user names a project or asks "where were we":
- Read
~/.jarvis/memory/<project>.md - Report back in 3 lines: last session date + what was done, current Next, open bugs count
- Then just start on Next unless told otherwise
Rules
- Facts, not vibes: "fixed N+1 in /api/orders (commit abc123)" beats "improved performance"
- Convert relative dates to absolute — "tomorrow" is meaningless in two weeks
- Never store secrets in memory files
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.