AI Memory Routing Install
Use this skill for any request to install, refresh, repair, inspect, or remove...
Install
npx skills add akitaonrails/ai-memory --skill ai-memory-routing-install -g -a claude-code -y- Repository
- akitaonrails/ai-memory14.8k
- Category
- AI and agents
- Updated
- 4d ago
- License
- MIT
- Context cost
- Lightabout 1,016 tokens
- Runs scripts
- No, instructions only
What it does
Use this skill for any request to install, refresh, repair, inspect, or remove ai-memory's agent-facing routing: managed instruction snippets, Agent Skills, CLAUDE.md/AGENTS.md integration, or local/global skill roots. Trigger by semantic intent rather than exact wording.
ai-memory routing install
Use this skill when the user wants ai-memory's agent-facing routing instructions or managed Agent Skills installed, refreshed, repaired, or removed.
Tools in this cluster
memory_install_self_routingreturns the canonical markered instruction block, marker strings, filename hints, notes, and managed skill payloads for agents that cannot let the MCP server write the host filesystem directly. Passcompact: truewhen managed Agent Skills are installed or when refreshing a file that already uses the compact snippet.
Managed instruction marker
The always-loaded instruction block is owned by ai-memory only between these markers.
- Start marker:
<!-- ai-memory:start --> - End marker:
<!-- ai-memory:end -->
Refresh must replace the first complete marker-bounded block whose start and end delimiters appear alone on their own lines, preserving unrelated content before and after it. Ignore inline mentions of marker strings inside prose or code; they are not delimiters. If no complete line-delimited block exists, append the canonical block with one blank line of separation. Never edit unrelated instructions while refreshing ai-memory routing.
Managed skill marker
Every ai-memory-managed SKILL.md file contains this ownership marker.
<!-- ai-memory-managed: routing-skill -->
Installers and uninstallers should overwrite or remove same-name skill files only when that marker is present, unless the user supplied an explicit force option. If a same-name skill lacks the marker, skip it with an actionable message so user-authored skills are preserved.

