asklisted

Use proactively mid-task, on your own initiative, whenever past work might already cover the current step — before re-fixing a recurring or previously-seen bug, touching an unfamiliar subsystem, or making a risky/hard-to-reverse change — not only when asked. Also when the user wants to recall prior context: 'what did we decide about X', 'find everything about Y', 'что мы решили про', 'что мы знаем', 'как мы делали', 'когда последний раз', 'такое уже было', 'вспомни', 'напомни', 'посмотри в памяти', 'найди в памяти', 'как решали', 'где ещё может быть', 'что было с', or similar. Synthesizes across notes with source citations; prefer over generic memory tools when an Obsidian vault is available.
jojoprison/mnemo · ★ 6 · AI & Automation · score 81

Install: claude install-skill jojoprison/mnemo

# mn:ask — Vault Knowledge Search & Synthesis > **Invocation marker (both runtimes):** begin your reply with the exact line `🧠 mn:ask (mnemo) → running` — the user-visible confirmation that this skill actually loaded. Emit it once per invocation, before any other output. ## Portable paths Resolve `<mnemo-root>` once to the absolute plugin root before reading bundled files or running bundled scripts. In Claude Code, use `${CLAUDE_PLUGIN_ROOT}`; in Codex, derive it from this loaded `SKILL.md` path (skill directory → `skills/` → plugin root). Replace `<mnemo-root>` with that quoted absolute path in every command — never execute the placeholder literally and never hunt versioned cache directories. When another mnemo skill must run, use the runtime-native path: Claude Code invokes `mn:<skill>` through its Skill tool; Codex reads `<mnemo-root>/skills/<skill>/SKILL.md` completely and follows it with the prepared input. For user-facing explicit syntax, render `/mn:<skill>` in Claude Code and `$mnemo:<skill>` in Codex. Search across the entire vault, read relevant notes, and synthesize an answer with source citations. ## Prerequisites & config Obsidian must be open. Config at `~/.mnemo/config.json` — reads `vault`, `links_section`, `taxonomy`, and `taxonomy_roles`. Before resolving a semantic type, require exactly the five role keys `fact`, `insight`, `source`, `session`, and `moc`; require every target to exist in `taxonomy`; and require `session → session` plus `moc → moc`.