distill-session
Skill17 starsChanged 7 months agoMITView on GitHub
Compress and save the key context from this session to the daily log. Run before ending a long session.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- gofixpoint/amikatheir own version, first seen Oct 8, 2026
- rajdeep-singha/SecondBraintheir own version, first seen Sep 5, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- gofixpoint/amika★ 305same name
- rajdeep-singha/SecondBrain★ 2same 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 repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- daily-standupSkill
- heartbeatSkill
- humanizerSkill
- memory-updateSkill
- playwright-cliSkill
- promoteSkill
- researchSkill
- search-memorySkill
- self-improveSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 13
Create the file with a # Daily Log — YYYY-MM-DD header if it doesn't exist
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Session distillation — save this session's context to the daily log:
- Summarize what was accomplished in this session (3-5 bullets)
- List any open tasks or threads left unfinished
- Extract any preferences or patterns {{OWNER_NAME}} demonstrated
- Append to
daily-logs/YYYY-MM-DD.md(today's date) under a## [HH:MM] Session Distillheading- Create the file with a
# Daily Log — YYYY-MM-DDheader if it doesn't exist
- Create the file with a
- Also append a one-liner to
identity/memory.mdunder## Session Log: Format:- [YYYY-MM-DD] <what was done, 1 line> - Confirm what was saved
Token budget: keep the daily log entry under 200 words. Keep the identity/memory.md one-liner under 20 words.
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.

