agentleFS
opendatadiscoveryopendatadiscovery/odd-team/.claude/skills/navigate/SKILL.md

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

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
  1. Very specific:

    If match: read and display the relevant navigation/domains/{feature}.md

    line 16
  2. Very specific:

    If no match: grep across all navigation/domains/*.md for the keyword

    line 17
  3. Distinctive:

    Update navigation: add discovered paths to the relevant domain file

    line 26
  4. Distinctive:

    Always try navigation index FIRST — it's the whole point of this system

    line 35
  5. Distinctive:

    If navigation is empty/stale for this feature, fix it as part of answering

    line 36
  6. Distinctive:

    Keep output concise — show file paths, not file contents

    line 37
  7. Distinctive:

    If multiple domains match, list them and ask which to drill into

    line 38

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Navigate

Find code locations for $ARGUMENTS.

Protocol

  1. Search navigation index — Check in order:
    • navigation/features.yaml — does $ARGUMENTS match a domain name or summary?
    • If match: read and display the relevant navigation/domains/{feature}.md
    • If no match: grep across all navigation/domains/*.md for the keyword
  2. If found in navigation — Display:
    • The domain file contents (code entry points, tests, docs, related domains)
    • Highlight the most relevant paths for the query
  3. 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
  4. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.