memory-promotelisted

Audit this repo's auto-memory files and suggest promoting each one to a more persistent layer — user or repo CLAUDE.md, an existing or new skill, a settings.json hook, or a checked-in reference doc. Use when the user says "audit memory", "promote memory", "clean up memories", "memory-promote", or wants to move ephemeral memory into durable config.
lttr/claude-marketplace · ★ 2 · Data & Documents · score 78

Install: claude install-skill lttr/claude-marketplace

# Memory Promote Auto-memory under `<config-dir>/projects/<encoded-cwd>/memory/` is per-conversation context, not durable config. Many memories belong in a more persistent layer where they apply consistently and survive memory pruning. This skill scans memories and proposes a target layer for each. `<config-dir>` is `$CLAUDE_CONFIG_DIR` when set, otherwise `~/.claude`. Resolve it once at the start and use it everywhere below. ## Scope The current repo. Memory dirs encode the absolute cwd with `/` replaced by `-`: - `/home/alex/work/api` → `<config-dir>/projects/-home-alex-work-api/memory/` Compute `MEM_DIR="$CONFIG_DIR/projects/$(pwd | tr / -)/memory"`. If it doesn't exist, report "no memories for this repo" and stop. If the user asks for something wider or narrower in their own words — another repo, every project, only the cross-cutting ones, just list them without suggestions — honor it using the same encoding. Don't invent flags for it; the report-then-confirm loop below already gives them control. ## Steps 1. **List memories.** `find "$MEM_DIR" -type f -name '*.md' ! -name 'MEMORY.md'`. For each file, read the frontmatter and body. Memory frontmatter looks like: ```yaml --- name: coolify-deploy description: Deployment coordinates for the app metadata: node_type: memory type: project originSessionId: <uuid> --- ``` The classification key is `metadata.type` (commonly `user`, `project`, `feedback`, `reference`). If it is abse