mnemo-memorylisted

# mnemo Memory Use mnemo MCP tools to recover and persist project knowledge across sessions. Keep the always-active project instructions authoritative; this skill provides the detailed workflow. ## 1. Verify the project Before any memory operation: 1. Resolve the Git repository root, or use the current workspace when it is not a Git repository. 2. Read `<root>/.mnemo`. 3. Continue only when it is valid JSON with a non-empty `id`. 4. Use that `id` as `project` in every mnemo tool call. If `.mnemo` is missing or invalid, tell the user to run `mnemo init` and stop the memory workflow. If mnemo tools are unavailable, report that integration is incomplete. Never create `MEMORY.md`, write into an agent's native memory directory, or use arbitrary text files as a fallback. ### Troubleshoot integration When mnemo appears misconfigured, unavailable, or inconsistent with the project marker, prefer the read-only diagnostic command before guessing: ```bash mnemo doctor --path <root> mnemo doctor --json --path <root> ``` Use the output to explain missing `.mnemo`, PATH, global instruction, MCP, hook/plugin, or store issues. Do not repair global setup automatically unless the user explicitly asks for setup or install changes. ### Database upgrade recovery mnemo applies safe database migrations automatically when any CLI, MCP, or hook path opens the store. If an older local database is detected, the normal agent workflow should recover it without a separate user decision. If a mn