Cortex Debug Memory
Skill Verified ActiveDebug 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.
Debug and fix memory system issues by validating, rating, protecting, forgetting, and restoring memories to ensure accurate and relevant agent recall.
Features
- Soft and hard deletion of memories
- Rating memory usefulness to train confidence models
- Anchoring critical memories for permanent protection
- Validating memories against filesystem references
- Saving and restoring memory checkpoints
Use Cases
- Use when agent recall returns incorrect or stale results
- Use when needing to undo recent changes to agent memory
- Use to improve retrieval quality by providing feedback on memory usefulness
- Use to protect important architectural decisions or facts from decay
Non-Goals
- Managing general agent configuration
- Executing arbitrary code
- Modifying external project files directly (other than memory validation)
Workflow
- Identify the memory operation needed (forget, rate, protect, validate, checkpoint).
- Call the appropriate `cortex` tool with the required parameters (e.g., memory_id, useful=true, directory).
- Observe the outcome, such as memory deletion, confidence score adjustment, or a list of stale memories.
Installation
First, add the marketplace
/plugin marketplace add cdeust/Cortex/plugin install Cortex@cortex-pluginsQuality Score
VerifiedTrust Signals
Similar Extensions
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Ctx Doctor
100Run context-mode diagnostics. Checks runtimes, hooks, FTS5, plugin registration, npm and marketplace versions. Trigger: /context-mode:ctx-doctor
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Playwright Best Practices
100Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.