memory-cleanuplisted

# Memory Cleanup ## Overview Hermes core memory is deliberately small. `MEMORY.md` and `USER.md` are injected into the prompt at session start, so every stale sentence is paid for on every turn of that session. The goal of this skill is to cut memory size, often by half, **without losing data or important instructions**. This is not a deletion pass. It is a routing pass. Each fact moves to the smallest correct home: 1. **Compress in place** when the fact truly belongs in core memory. 2. **Relocate** to a better always-on file (`SOUL.md`, `USER.md`, a project `AGENTS.md`, or a context file) when the fact is not agent-memory. 3. **Offload** long-tail searchable context to the configured memory provider when it should be retrievable but not always in the prompt. 4. **Convert to a skill** when the entry is a reusable procedure, workflow, or hard-won how-to. 5. **Drop** only when the entry is stale, duplicated, already captured elsewhere, or will be wrong soon. Default mode is **dry run**. The agent running this skill must not edit live memory until the proposed diff has been reviewed and approved. ## Target Parameter This skill accepts an optional cleanup target that sets how aggressive the diet should be. Accept it in whatever form the user gives it and normalize to an absolute character goal for `MEMORY.md`: - A percentage, for example `50%`, means cut `MEMORY.md` to half its current size. - An absolute size, for example `5000` or `5000 chars`, means get `ME