setup

# mn:setup — Interactive Onboarding > **Invocation marker (both runtimes):** begin your reply with the exact line `🧠 mn:setup (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. First-time setup for mnemo. Creates config.json with all settings. ## Workflow ### Step 1: Welcome ``` 🧠 Welcome to mnemo — persistent memory for Codex and Claude Code. Let's set up your configuration. This takes about 30 seconds. ``` ### Step 2: Vault Name ``` What's your Obsidian vault name? (The name shown in Obsidian's vault switcher) > main ``` Verify vault exists: ```bash python3 "<mnemo-root>/scripts/safe-read.py" search <<'JSON' {"query":"test","vault":"{i...