cortex-debug-memory

Solid

Debug and fix memory system issues — validate memories, rate quality, manage protection, forget bad memories, and restore from checkpoints. Use when the user says 'fix memory', 'bad memory', 'wrong memory', 'delete this', 'protect this', 'this memory is wrong', 'memory quality', 'rate this memory', 'restore checkpoint', 'undo', or when memories are returning incorrect or stale results.

AI & Automation 68 stars 11 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
61
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Debug Memory — Fix, Rate, Protect, and Restore ## Keywords debug, fix, bad memory, wrong, delete, forget, protect, rate, quality, restore, checkpoint, undo, stale, incorrect, mark useful, mark not useful, anchor, unprotect ## Overview Tools for maintaining memory quality — rate memories as useful or not, protect critical ones from decay, forget incorrect ones, validate against the filesystem, and restore from checkpoints when things go wrong. **Use this skill when:** Recall returns wrong results, memories are stale, you need to undo changes, or you want to improve retrieval quality through feedback. ## Workflow ### Fix Bad Memories **Soft delete** (sets heat to 0, memory still exists but won't surface): ``` cortex:forget({ "memory_id": <id>, "hard": false }) ``` **Hard delete** (permanent removal): ``` cortex:forget({ "memory_id": <id>, "hard": true }) ``` Protected memories require `"force": true` to delete. ### Rate Memory Quality Provide feedback to train the metamemory confidence model: ``` cortex:rate_memory({ "memory_id": <id>, "useful": true }) ``` Or mark as not useful: ``` cortex:rate_memory({ "memory_id": <id>, "useful": false, "reason": "outdated — we no longer use this approach" }) ``` Ratings adjust the memory's confidence score, which affects future retrieval ranking. Over time, this trains the system to surface better results. ### Protect Critical Memories **Anchor** a memory (heat=1.0 permanently, injected at session start):...

Details

Author
cdeust
Repository
cdeust/Cortex
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

cortex-explore-memory

Explore the memory system's state, find gaps in knowledge, assess coverage, and get diagnostic information. Use when the user asks 'what does my memory look like', 'show me memory stats', 'what am I missing', 'how good is my knowledge', 'memory health', 'show coverage', 'find gaps', 'what topics are weak', or when you need to understand the state of stored knowledge before a task.

68 Updated today
cdeust
AI & Automation Solid

cortex-consolidate

Run memory maintenance — decay old memories, compress stale content, consolidate episodic memories into semantic knowledge, and run sleep-like replay. Use when the user says 'clean up memories', 'consolidate', 'run maintenance', 'compress old memories', 'memory cleanup', or periodically to keep the memory system healthy. Also use after importing many memories or at the end of a long session.

68 Updated today
cdeust
AI & Automation Listed

bettermemory

Verification-grade memory between sessions. Use bettermemory's MCP tools (memory_search, memory_show, memory_write, memory_verify, memory_record_use, etc.) instead of writing to files when the user asks you to "remember" something or references shared context from a past session. Default is to NOT call memory_search; only retrieve when the user references context you don't have ("my project", "the script we wrote") or a request is ambiguous in a way stored preferences could resolve. Every hit carries a staleness_verdict (calendar + path-drift + commit-drift); when it isn't "fresh", spot-check a claim before relying and call memory_verify to attest. Every use should record a claim_excerpt so retrievals stay auditable.

0 Updated today
0Mattias