repo-atlas
Skill0 starsChanged 18 days agoNo licenceView on GitHub
Build a single-file HTML learning map for one GitHub repository or local clone: an architecture map with a trunk scenario, an 8-10 stop learning path, evidence-tagged facts, history turning points, risks, and a hidden handoff block so a later agent can update it. Read-only on the target repo. Use when the user asks for a learning map, architecture map or atlas of a repo, or wants to onboard onto an unfamiliar codebase through a visual map. 中文触发:给这个仓库做学习地图、架构地图、读懂这个 repo、repo atlas。
4 other projects use a version of this.
Adopted by
Most recently taken up by
- cathrynlavery/repo-atlastheir own version, first seen Nov 6, 2026
- AndreaMontemaggiore1/repo-atlastheir own version, first seen Nov 1, 2026
- vivekmaru/repo-atlastheir own version, first seen Oct 20, 2026
- Lxiny-zy/repo-atlastheir own version, first seen Oct 5, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- cathrynlavery/repo-atlas★ 56same name
- Lxiny-zy/repo-atlas★ 13same name
- AndreaMontemaggiore1/repo-atlas★ 2same name
- vivekmaru/repo-atlas★ 0same 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.
- ai-dailySkill
- ask-questionsSkill
- astryx-frontendSkill
- aws-cliSkill
- cf-cliSkill
- codex-usageSkill
- codex-wallpaperSkill
- creativeSkill
- daily-job-applySkill
- daily-readSkill
- dating-timeSkill
- draw-somethingSkill
- fs-streetSkill
- gh-address-commentsSkill
- gh-fix-ciSkill
- gh-resume-builderSkill
- gmail-ai-daily-opsSkill
- grok-remoteSkill
- imagegenSkill
- job-apply-automationSkill
- job-search-orchestratorSkill
- job-searchSkill
- lark-history-exporterSkill
- lavayou-author-lensSkill
- linkedin-application-agentSkill
- migrate-to-codexSkill
- obsidianSkill
- openai-docsSkill
- opentrain-application-agentSkill
- pdf-sanitizeSkill
- pdfSkill
- stripe-cli-opsSkill
- wezterm-wallpaperSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
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.

