memory-maintenance

Curates persistent file-based memory by deduplicating, structuring, and routing facts without data loss.

23|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Alexey-Lukin/silken_net --skill memory-maintenance-alexey-lukin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-maintenance
Source: https://github.com/Alexey-Lukin/silken_net/tree/main/.claude/skills/memory-maintenance
Command: npx skills add https://github.com/Alexey-Lukin/silken_net --skill memory-maintenance-alexey-lukin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Persistent file-based memory (MEMORY.md plus per-fact markdown files) accumulates cruft, duplicates, stale index hooks, and untracked action items over time, and naive cleanup risks deleting valuable lessons and decisions. This Skill provides a disciplined playbook for curating that memory corpus while preserving every fact that still matters. ## Core Features & Use Cases - Structured housekeeping: Groups the memory index by kind, trims bloated index hooks, fixes stale hooks that drifted from their files, and verifies 1:1 index-to-file integrity. - Zero-loss deduplication: Removes only truly dead content after verifying it lives elsewhere, with verbatim-reorder scripts and git-diff proofs that nothing was lost. - Type-routing of facts: Routes each fact to its correct home — domain skill, canon docs, memory, or playbook — and migrates open action items into the 00_07 tracker with back-pointers. - Curation trap catalog: Ships a traps.md companion documenting 19 measured pitfalls (scout undercounting, bilingual dedup blindness, false homelessness) to consult before any consolidation verdict. - Use Case: When the memory index has grown bloated and you suspect duplicated rules across memory files, skills, and docs, invoke this Skill to run the gate audit, consolidate scattered classes into single homes, and report honestly what was cleaned versus deliberately kept. ## Quick Start Use the memory-maintenance skill to audit my memory corpus, remove duplicates, fix stale index hooks, and make sure every open action item is tracked in 00_07.

Frequently Asked Questions about memory-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up a bloated AI memory file without losing information?

Run the memory gate audit first, then trim bloated index hooks only after verifying the detail exists in the target file. Use verbatim-reorder scripts with a sorted entry-set diff to prove zero loss, and prefer relocating content over deleting it.

How to deduplicate facts spread across memory files and skill documents?

Start with the gate's verbatim overlap detection, then inventory by reading, because machine dedup only catches verbatim copies and bilingual corpora hide an order of magnitude more. Consolidate each duplicated class into one home and replace other copies with link pointers.

What is type-routing for persistent memory facts?

Type-routing assigns each fact a home by its nature: operational how-to goes to a domain skill, shipped decisions go to canon docs, live state and lessons stay in memory, and portable work rules go to the relevant playbook. The routing decision happens at write time.

Why does grep-based duplicate detection miss most duplicates?

Grep and shingle-based checks are capped at verbatim matches, so paraphrased or translated restatements are invisible to them. On a bilingual corpus the gap reaches an order of magnitude, so a clean automated result only means no verbatim duplicates exist.

When should memory content be migrated to a tracker instead of deleted?

Open action items, to-dos, and follow-ups found in memory should be migrated into the external tracker under the correct section, with a back-pointer left in the memory file. Deletion is only acceptable for truly dead content verified to exist elsewhere.