repo-map
Skill1 starsChanged 45 days agoMITView on GitHub
Understand a repository's structure without reading files. Use when orienting in an unfamiliar codebase, finding where a symbol is defined, outlining a single file, or locating entry points before editing.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- PeanutGT/NutsSkillstheir own version, first seen Nov 8, 2026
- jocarrd/crux-agentstheir own version, first seen Nov 8, 2026
- idaibin/skillstheir own version, first seen Nov 8, 2026
- Tcuzzo/backs-aios-skillstheir own version, first seen Nov 3, 2026
- marinvch/Cortextheir own version, first seen Nov 1, 2026
- Rktmkalita/claude-skillstheir own version, first seen Nov 1, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- AnastasiyaW/claude-code-config★ 214same name
- AnastasiyaW/codex-claude-code-config★ 214same name
- ejboy/agent-scripts★ 116same name
- idaibin/skills★ 6same name
- yeaight7/agent-powerups★ 6same name
- jocarrd/crux-agents★ 4same name
- PeanutGT/NutsSkills★ 3same name
- mmaripanguec/dev-sdd-kit★ 2same name
- Tcuzzo/backs-aios-skills★ 2same name
- David-Florian2013/Stop-trusting-made-it-faster-here-is-5-best-skills-for-Claude-★ 1same name
3 more not listed
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 repository9 other files it gives its agents.
- commitsmithSkill
- context-budgetSkill
- gatewaySkill
- injection-guardSkill
- json-lensSkill
- log-tailSkill
- secret-scanSkill
- tokensaverSkill
- web-snapshotSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Call repo_map with the repository root before opening any file.
- Very specific: line 30
Use find_symbol to jump straight to a definition instead of grepping.
- Very specific: line 31
Use file_outline before reading a large file.
- Distinctive: line 32
When the budget truncates, narrow the path or raise the budget.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repository map
Get the shape of a repository — tree, languages, entry points, and key symbols — in one budgeted call instead of reading dozens of files.
MCP tools
| Tool | Use it for |
repo_map | First look: tree, language stats, entry points, exported symbols. |
find_symbol | Where is X defined? Returns file, line, kind, visibility. |
file_outline | The shape of one file with line ranges (methods included). |
entry_points | How does this project start executing? |
Workflow
- Call
repo_mapwith the repository root before opening any file. - Pick the files that matter from the map.
- Use
find_symbolto jump straight to a definition instead of grepping. - Use
file_outlinebefore reading a large file. - When the budget truncates, narrow the path or raise the budget.
CLI fallback
npx -y tokensaver-mcp # same tools over MCPTips
- Entry points usually appear in
package.json(bin,main,exports) and the tree marks them with*. - The map respects
.gitignore(including nested files) and skips dependencies automatically.
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.