memory-compaction
Skill1 starsChanged 2 days agoMITView on GitHub
Compact the client's memory: a week folds into journal lines, a quarter into a summary, and MEMORY.md stays a short index. Use at the retro at the end of the week and once a month.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- makushingu/harness-maxxingtheir own version, first seen Nov 8, 2026
- Archive228/lab-skillstheir own version, first seen Aug 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- makushingu/harness-maxxing★ 235same name
- Archive228/lab-skills★ 8same 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 repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-visualizationSkill
- approval-packSkill
- content-atomizationSkill
- dispatchSkill
- fact-checkSkill
- ffmpeg-skillSkill
- hook-storylineSkill
- idea-diceSkill
- jurySkill
- perf-loopSkill
- publish-kitSkill
- seamless-insertSkill
- setupSkill
- shoot-briefSkill
- sound-designSkill
- source-skeletonSkill
- style-memorySkill
- treg-gatewaySkill
- trend-scoutSkill
- utmSkill
- video-codeSkill
- weekly-cycleSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Update memory/MEMORY.md as an index (≤ 200 lines):
- Distinctive: line 26
Check for repeats: topics that came out ≥ 3 times in 2 months → "on pause".
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Memory compaction
Goal: at the start of work the agent reads little but knows the essentials: what has already happened, what works, where we are now.
Weekly (after the retro)
- For each published unit, one line in
memory/published-log.md:| 2026-10-21 | W43-R02 | instagram | Site walkthrough | finished install on site, "no drafts" | pain_direct | reels/f01 | 2.4 | WIN | - Full scripts and files stay in
weeks/<W>/(this is the archive; it is not read by default). - Update
memory/MEMORY.mdas an index (≤ 200 lines):- state (onboarding, current week, open questions);
- the 3–5 main conclusions of recent weeks with links to files;
- topics on pause (overheated) and candidate topics;
- the client's latest feedback in one line.
Monthly
- Fold
published-loglines older than a quarter into a "Summaries" block: "Q3: 12 Reels about installation; best performer: before/after with a number in the first line (median ×1.9); the 'prices' topic is overheated — paused until December". - In
targeting-map,hooks-libraryandplatform-learnings: delete conclusions refuted by fresh data (with a note inchangelog.md). - Check for repeats: topics that came out ≥ 3 times in 2 months → "on pause".
Where to remember what (short)
| What | Where | Changed by |
| Business, product, taboos, permissions | passport.yaml, product-base/, permissions.yaml, CLAUDE.md | human only (locked layer) |
| Style and tone, learned rules | brand/voice.md, brand/visual.md, brand/tokens.json | feedback, with evidence |
| What was published | memory/published-log.md | retro |
| What works | targeting-map, hooks-library, platform-learnings, channel-state | analyst |
| Numbers | analytics/*.jsonl | scripts only |
| Golden references and assets | brand/golden/, brand/assets/, Drive | feedback, human |
| An agent's experience in its own craft | .claude/agent-memory/<agent>/MEMORY.md | the agent itself (not about the client) |
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.

