navigator
Skill0 starsChanged 10 months agoMITView on GitHub
Specialized in codebase exploration, finding file paths, tracing execution logic, and mapping dependencies. Use when exploring unfamiliar codebases, finding where code is located, tracing function calls, understanding module structure, or mapping system dependencies.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- noxxer/core-teamtheir own version, first seen Nov 13, 2026
- Curious-Keeper/skillstheir own version, first seen Oct 8, 2026
- buriedsignals/spotlighttheir own version, first seen Aug 26, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- buriedsignals/spotlight★ 60same name
- noxxer/core-team★ 4same name
- Curious-Keeper/skills★ 1same 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 repository33 other files it gives its agents.
- architectSkill
- brainstormingSkill
- concise-planningSkill
- context-engineerSkill
- data-deprecation-analysisSkill
- data-modelerSkill
- data-pipeline-engineerSkill
- data-quality-frameworksSkill
- dbt-transformation-patternsSkill
- github-workflow-automationSkill
- guardianSkill
- implementerSkill
- json-to-pydanticSkill
- llm-app-patternsSkill
- ops-managerSkill
- orchestratorSkill
- principal-data-engineerSkill
- product-manager-toolkitSkill
- proj-memorySkill
- prompt-librarySkill
- qa-testerSkill
- researcherSkill
- senior-data-engineerSkill
- software-architectureSkill
- spark-optimizationSkill
- sql-optimization-patternsSkill
- state-managerSkill
- subagent-driven-developmentSkill
- thinkerSkill
- top-web-vulnerabilitiesSkill
- verification-before-completionSkill
- web-design-guidelinesSkill
- workflow-managerSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 23
Discovery: Use find_by_name and list_dir to map directory structures.
- Very specific: line 24
Symbol Search: Use grep_search to find classes, functions, or specific strings across the project.
- Distinctive: line 42
Every navigation task should summarize:
- Distinctive: line 51
When entering a new or unfamiliar codebase.
- Distinctive: line 52
Before implementation to verify "where to cut" into the code.
- Distinctive: line 53
When trying to find the source of a specific error or behavior.
- Distinctive: line 66
DO NOT hallucinate paths: Only report what tools find.
- Distinctive: line 71
Missing File References: Not tracing all imports means some related files are missed.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Navigator Skill - Filesystem & Logic Discovery
Overview
The Navigator skill is the "GPS and Surveyor" of the codebase. It helps understand "where things are" and "how they work" before any changes are made.
Core Capabilities
1. Filesystem Scouting (Locator)
- Discovery: Use
find_by_nameandlist_dirto map directory structures. - Symbol Search: Use
grep_searchto find classes, functions, or specific strings across the project. - Context Extraction: Identify relevant files for a specific feature or bug without reading entire contents.
2. Logic Analysis (Analyzer)
- Execution Tracing: Map data flows from entry points to persistence.
- Dependency Analysis: Identify what a module relies on and what relies on it.
- Integration Seams: Pinpoint the exact location where a new feature should be injected or a bug fix should be applied.
Workflow
- Locate: Find all files related to the user's request using naming conventions and content searches.
- Read & Trace: Ingest the relevant files and follow imports/calls to understand the chain of command.
- Explain: Summarize the logic in plain English for implementation planning.
- Handoff: Provide a clear list of files and specific line numbers for the next phase.
Output Format: Discovery Report
Every navigation task should summarize:
- Relevant Files: List of absolute paths with a 1-sentence description of their role.
- Logic Summary: Explanation of the current execution flow.
- Dependency Map: Visual or text-based map of module interactions.
- Recommended Seam: Where modifications should specifically take place.
When to Use
- When entering a new or unfamiliar codebase.
- Before implementation to verify "where to cut" into the code.
- When trying to find the source of a specific error or behavior.
Outputs & Deliverables
- Primary Output: Discovery report summarizing relevant files, logic summary, and recommended seam (plain-text or markdown)
- Secondary Output: File list with line references and a short dependency map (Mermaid or ASCII)
- Success Criteria: Report identifies the correct set of files and a clear recommended modification seam
- Quality Gate:
implementerorarchitectconfirmation before changes are made
Constraints
- NO implementation or refactoring.
- NO writing to files.
- DO NOT hallucinate paths. Only report what tools find.
Common Pitfalls
- Incomplete Symbol Search: Searching for "user" finds hundreds of matches. Use more specific patterns and context to narrow results.
- Missing File References: Not tracing all imports means some related files are missed. Follow the import chain completely.
- Misreading Execution Flow: Assuming linear execution without understanding async/callbacks/events leads to wrong seams. Trace carefully.
- Ignoring Circular Dependencies: Finding mutual imports indicates a design problem. Flag these as risks, not just connections.
- Wrong Modification Point: Recommending changes at the wrong layer. Understand the full flow before suggesting "cut here".
- Hallucinated Files: Inventing file paths that don't exist. Only report paths confirmed by directory listings and searches.
Integration Points
| Phase | Input From | Output To | Context |
| Exploration | User question about codebase | Discovery report | Find relevant files and logic flow |
| Validation | Report findings | implementer | Confirm modification seam is correct |
| Architecture | System understanding | architect | Provide dependency map for design decisions |
| Implementation | Ready-to-code state | implementer | List exact files and line numbers for changes |
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.

