← ClaudeAtlas

memexlisted

Route Memex requests to the correct code, personal, graph, ingestion, query, update, or operations workflow. Use when a user asks to create, inspect, refresh, search, understand code structure, diagnose, schedule, or remove a Memex and the correct specialized workflow is not yet selected.
giulioleone097/memex · ★ 0 · AI & Automation · score 70
Install: claude install-skill giulioleone097/memex
# Memex router Select one workflow. Keep Codex and Claude Code on the same deterministic runtime and wiki state. ## Host paths - Codex: derive the plugin root from this SKILL.md path by removing `/skills/memex/SKILL.md`; never derive it from the current working directory. - Claude Code: use `${CLAUDE_PLUGIN_ROOT}` as the plugin root. - Define `<cli>` as `node "<plugin-root>/dist/cli.js"` for Codex or `node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js"` for Claude Code. ## Preconditions - Require Node.js 20 or newer. - Determine mode explicitly: `code` writes `<repository>/memex/`; `personal` writes `~/.memex/wiki/`. - Resolve the requested root before any mutation. Do not infer personal mode from a missing Git repository. - Confirm that external connector reads, when requested, use a host-authorized tool. ## Procedure 1. Run `<cli> status --mode <mode> --root <root> --json`; accept `NOT_INITIALIZED` only when initialization is the requested next action. 2. Route repository structure, symbol, dependency, architecture, impact, or changed-path questions to `memex-graph` in code mode. Route creation to `memex-init`, wiki refresh to `memex-update`, grounded page questions to `memex-query`, external-source reads to `memex-ingest`, and doctor, schedule, recovery, purge, privacy, or uninstall to `memex-ops`. 3. Load only the selected specialized skill and follow its operation order without substituting upstream Memex commands. 4. Return the selected mode, root, workflow, mutation level,