navigate
Skill0 starsChanged 2 months agoApache-2.0View on GitHub
Find where a feature, component, or concept lives in the ODD codebase. Uses the navigation index for O(1) lookups.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- boshu2/agentopstheir own version, first seen Jul 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- boshu2/agentops★ 454same name
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 repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- alignSkill
- code-walkSkill
- conceptsSkill
- contributeSkill
- coverageSkill
- doc-gap-checkSkill
- enrichSkill
- enumerateSkill
- find-implicit-adrsSkill
- implementSkill
- ingest-docsSkill
- log-issueSkill
- next-batchSkill
- orientSkill
- panelSkill
- probe-defineSkill
- probe-runSkill
- probeSkill
- reflect-featureSkill
- retrieveSkill
- reviewSkill
- scanSkill
- statusSkill
- streamsSkill
- test-coverageSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
If match: read and display the relevant navigation/domains/{feature}.md
- Very specific: line 17
If no match: grep across all navigation/domains/*.md for the keyword
- Distinctive: line 26
Update navigation: add discovered paths to the relevant domain file
- Distinctive: line 35
Always try navigation index FIRST — it's the whole point of this system
- Distinctive: line 36
If navigation is empty/stale for this feature, fix it as part of answering
- Distinctive: line 37
Keep output concise — show file paths, not file contents
- Distinctive: line 38
If multiple domains match, list them and ask which to drill into
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Navigate
Find code locations for $ARGUMENTS.
Protocol
- Search navigation index — Check in order:
navigation/features.yaml— does$ARGUMENTSmatch a domain name or summary?- If match: read and display the relevant
navigation/domains/{feature}.md - If no match: grep across all
navigation/domains/*.mdfor the keyword
- If found in navigation — Display:
- The domain file contents (code entry points, tests, docs, related domains)
- Highlight the most relevant paths for the query
- If NOT in navigation — Fall back to search:
- Grep across repo directories for the keyword
- Report what you find
- Update navigation: add discovered paths to the relevant domain file
- Tell the user the navigation has been enriched for next time
- Cross-repo view — If the feature spans repos:
- Show entry points in each repo
- Show the connection between them (e.g., "spec defines it → platform implements it → collectors populate it")
Rules
- Always try navigation index FIRST — it's the whole point of this system
- If navigation is empty/stale for this feature, fix it as part of answering
- Keep output concise — show file paths, not file contents
- If multiple domains match, list them and ask which to drill into
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.

