ai-memory-routing-install
Skill0 starsChanged 3 months agoMITView on GitHub
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.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- ton-anywhere/my-favorite-promptsedited, first seen Nov 8, 2026
- lucas-Oliveira-01/agentsedited, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- ton-anywhere/my-favorite-prompts★ 472% same
- lucas-Oliveira-01/agents★ 191% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-memory-durable-pagesSkill
- ai-memory-handoffSkill
- ai-memory-learning-maintenanceSkill
- ai-memory-retrievalSkill
- avc-amendSkill
- avc-build-sliceSkill
- avc-freeze-oracleSkill
- avc-live-qaSkill
- avc-retroSkill
- avc-reviewSkill
- avc-scoutSkill
- avc-spikeSkill
- avc-startSkill
- avc-verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill when the user wants ai-memory's agent-facing routing instructions or managed Agent Skills installed, refreshed, repaired, or …
- Very specific: line 26
Every ai-memory-managed SKILL.md file contains this ownership marker.
- Distinctive: line 49
Use platform-aware path joining.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- ai-memory-managed: routing-skill -->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.
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.
Skill install targets
Managed skills are ordinary Agent Skills. Their relative file path is <skill>/SKILL.md, and the installer prepends the selected skill root.
Project-local targets:
.claude/skills/<skill>/SKILL.mdfor Claude-compatible installs..agents/skills/<skill>/SKILL.mdfor cross-client installs..grok/skills/<skill>/SKILL.mdfor Grok Build CLI installs.
Global targets:
~/.claude/skills/<skill>/SKILL.mdfor Claude-compatible installs.~/.agents/skills/<skill>/SKILL.mdfor cross-client installs.$GROK_HOME/skills/<skill>/SKILL.mdfor Grok Build CLI installs (default:~/.grok/skills/<skill>/SKILL.md).
Use platform-aware path joining. Do not build paths by string concatenation.
Refresh guidance
For an agent-side refresh, call the install-routing tool. Its returned target_hints are authoritative for skill roots: choose the right instruction filename from agent_filenames, write the markered block with the agent's file-edit tool, and write each managed skill file below the selected hint using its relative_path. Claude Code normally uses CLAUDE.md and .claude/skills; Codex, OpenCode, Cursor, Gemini CLI, and AGENTS-aware clients normally use AGENTS.md and .agents/skills; Grok Build CLI uses AGENTS.md and .grok/skills unless the project says otherwise.
For a CLI refresh, prefer the canonical install command. The snippet and skills must be updated from the same core-owned assets so they do not drift.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.