memory-audit-cleanup-export-skill

Installation
SKILL.md

Memory Audit, Cleanup and Export

Authority and runtime first

Bind the user's task mode, accounts, stores, scope, exclusions and output. Apply current owner authority to evident in-scope audit fixes while respecting an explicit read-only or report-only request and higher-priority runtime rules. This skill supplies a procedure; it grants no independent permission to edit or delete memory. An export request alone does not authorize unrelated cleanup.

Inspect the current runtime's native memory instructions, exposed tools, schemas, authentication and persistence contract before selecting a route. Discovering a similarly named tool does not establish authority over this runtime's memory. Never substitute an unrelated application's memory namespace, including Notion, or infer that no memories exist from its empty result.

Use the supported native route. If direct mutation is forbidden, submit precise correction/deletion notes through the allowed route and report their actual state. Never use another executor, tool or filesystem route to bypass that boundary. Do not edit instruction files, code, skills or unrelated stores during a memory audit unless separately requested.

Inventory and source coverage

  1. Recover the existing relevant audit, review or export and its coverage, decisions, unresolved corrections and source locators. Reuse verified findings; inspect the changed delta and affected dependencies instead of restarting completed work.
  2. Enumerate every discoverable in-scope store and item, including project scopes and nested payloads. Record stable IDs/paths, versions, counts, pagination cursors and inaccessible slices in runtime context. Do not create a parallel tracker.
  3. Read every in-scope item in full through bounded pages or chunks before classification. Titles, descriptions, snippets and summaries are locators, not full coverage. Never force one giant dump or equate a sample with completion.
  4. Count items and, for text stores where meaningful, lines per store and in total. Distinguish entries, files and lines; state unknown counts rather than inventing them.
  5. Use available delegation only when permitted and useful for context or independent work. Assign disjoint read-only ranges and concise evidence returns; keep one mutation owner per store. No fixed file-count threshold mandates agents.

Recover decisive original conversations or source passages for material conflicts, owner preferences and changing project facts. Search exact entities/IDs and read the relevant complete segments. Use current primary records for present provider state. Chronicle, Screenpipe or other history can locate evidence when available and relevant; they do not supersede the underlying conversation, file or provider.

Installs
4
First Seen
Oct 22, 2026