agentleFS
Sign inStart free
RoentekRoentek/Claude_Code_Boilerplate_Framework/.claude/skills/compact-memory/SKILL.md

compact-memory

Skill4 starsChanged 6 months agoMITView on GitHub

Full memory hygiene cycle — compresses memory-sessions.md, deduplicates memory-decisions.md, and syncs key project facts to the memory MCP graph. Run monthly or when context feels heavy.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the following steps in order.

    line 6
  2. Very specific:

    Read .claude/rules/memory-sessions.md.

    line 10
  3. Very specific:

    Read .claude/rules/memory-decisions.md.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run the following steps in order. Report results after each step.

Step 1: Compress sessions

Read .claude/rules/memory-sessions.md. Summarize all entries older than 30 days into a ## Archive block. Keep the 4 most recent sessions in full. Rewrite the file.

Report: lines before → lines after.

Step 2: Prune decisions

Read .claude/rules/memory-decisions.md. Identify decisions whose tools, files, or patterns no longer exist in the project (check with Glob/Grep). Remove obsolete entries. Flag anything you removed so the user can restore it if needed.

Report: decisions before → decisions after, what was removed.

Step 3: Sync to knowledge graph

Extract 3–5 key project facts from the memory files (active integrations, key constraints, architectural choices). Write each as an entity to the memory MCP graph using mcp__memory__create_entities. This makes them queryable in future sessions without loading the full files.

Report: entities written.

Step 4: Summary

Print a single table: lines saved, decisions pruned, entities synced.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free