memory-review
Skill2 starsChanged 49 days agoMITView on GitHub
Review the session for stable learnings about the channel, the voice, the formats or the way of working, and propose memory updates for the creator to approve. Run by /remember, and offered before a long session is compacted. Triggered by "remember this", "save what we learned", "update the memory", "what did we learn today". In Spanish, "acuérdate de esto", "guarda lo que hemos aprendido", "actualiza la memoria", "qué hemos aprendido hoy".
6 other projects use a version of this.
Adopted by
Most recently taken up by
- cveralyon/axel-setuptheir own version, first seen Nov 8, 2026
- denormans/claude-code-workflowtheir own version, first seen Nov 8, 2026
- letsloose501/sqs-agent-memorytheir own version, first seen Nov 3, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
- dekimuhq/claude-memorytheir own version, first seen Jun 3, 2026
- finger88/my-claude-skillstheir own version, first seen Apr 7, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Hassaan146/claude-skills★ 18same name
- cveralyon/axel-setup★ 4same name
- finger88/my-claude-skills★ 3same name
- letsloose501/sqs-agent-memory★ 2same name
- denormans/claude-code-workflow★ 1same name
- dekimuhq/claude-memory★ 0same 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
- llms.txtllms.txt
- analyse-channel-packagingSkill
- analyse-thumbnailsSkill
- channel-analyticsSkill
- channel-identitySkill
- channel-kickoffSkill
- competitor-boardSkill
- competitor-ideationSkill
- competitor-mappingSkill
- competitor-scanSkill
- image-generation-coreSkill
- image-refinementSkill
- keywords-seoSkill
- likeness-preservationSkill
- monetisationSkill
- packagingSkill
- script-writingSkill
- thumbnail-best-practicesSkill
- thumbnail-inspirationSkill
- transparencySkill
- youtube-banner-specSkill
- youtube-profile-specSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
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 33
Find the home of each candidate: Update the file that already covers it.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Memory review
WHEN
At the end of a working session, when the creator asks to remember something, or when the session-start or pre-compaction notice suggests it. Always with the creator's approval before anything is written.
Memory is what turns a consultant into a coach, but only if what goes in is stable and true. A memory full of one-off remarks is noise the agent then obeys.
EXECUTION ORDER
- Read
memory/MEMORY.mdand the files it indexes that the session touched. Nothing is proposed without knowing what is already there. List the candidates. Go through the session and keep only what will still be true next month:
Keep Leave out A preference the creator stated or corrected ("tables, not prose") What only matters to today's task A prediction made and, later, its outcome Figures that a tool can measure again (store the date and the tool, not the number, unless it is an outcome) A format, pillar or positioning decision Guesses about why a metric moved: correlation is not a measurement A voice trait backed by a verbatim quote Anything the repo already records (tools, skills, config) - Find the home of each candidate. Update the file that already covers
it; create a new one only when none does, with the same front matter as the
rest (
name,description,metadata.type) and a line inMEMORY.md. memory/rules.mdis special. A candidate goes there only if the creator explicitly imposed it in this session. Quote their words and the date. A pattern you noticed is not a rule: propose it forcoach_preferences.mdor the journal instead, or leave it out.- Propose, do not write. Show each change as: file, the exact lines to add or replace, and why it is stable. Ask once for approval of the whole batch; the creator can drop items.
- Write only what was approved, then update
MEMORY.mdif a file was added or its status changed from not populated.
SOURCES
- The session itself and the tool outputs in it: every figure carried into
memory keeps the
sourcelabel and the date the tool returned it. memory/*.md:config, what was already stored.- Nothing in this skill calls the YouTube API or spends quota.
OUTPUT
A short list of proposed changes, grouped by file, each with its reason; then, after approval, one line per file saying what was written. If nothing stable came out of the session, say so in one line: an empty review is a valid result.
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.

