Repo map
Use when the task is to understand an unfamiliar codebase, locate key entry points, or summarize architecture before editing.From its SKILL.md
npx -y skills add yeaight7/agent-powerups --skill repo-mapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 383 tokens by cl100k_base, as published. Nobody here has run it
Purpose
Produce a structured overview of an unfamiliar codebase before making changes. Prevents wasted effort caused by misunderstanding project layout or entry points.
When to Use
- Starting work on an unfamiliar repository or module.
- Onboarding to a new project before the first edit.
- Locating where a feature lives before implementing or modifying it.
Do not edit code during this skill. Observation only.
Inputs
- Repository path or access to the codebase.
- Optional: specific area of interest (module, feature, data flow).
Workflow
- Identify project root, package manager, and language(s).
- Find main entry points (executables, API handlers, CLI commands).
- Read the smallest set of files needed to explain the architecture.
- Map major modules, their responsibilities, and how data flows between them.
- Flag risky or complex areas (high churn, missing tests, tangled dependencies).
Output
- Project purpose — What it does in one or two sentences.
- Entry points — Where execution starts.
- Main modules — What each major directory or package is responsible for.
- Data flow — How a typical request or operation moves through the system.
- Risky areas — Complex, undertested, or high-coupling zones to approach carefully.
Verification
- No code was edited during this skill
- All major modules identified
- Entry points documented
- Risky areas flagged
Failure Modes
- Premature editing — Do not make changes during mapping. Finish the map first.
- Monorepo confusion — Map each package or app separately if the repo contains multiple independent projects.
- Metaprogramming blind spots — Dynamic languages may have runtime-defined routes or classes. Note these as limitations in the output.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most codebase onboarding skills give in 383 tokens
Counted across 307 of the 325 authors here whose files we hold, read 2026-09-06
- Focus first session on one successful outcomein 34 of 307, across 15 files
- Show progress and celebrate completionsin 32 of 307, across 13 files
- Prefer interactive doing over tutorialsin 32 of 307, across 13 files
- Remove every step between signup and core valuein 32 of 307, across 13 files
- Keep checklists to 3-7 items ordered by valuein 32 of 307, across 13 files
- Read product marketing context before asking questionsin 28 of 307, across 13 files
- Focus fixes on the biggest funnel drop-offsin 22 of 307, across 7 files
- Define activation as the action most correlated with retentionin 20 of 307, across 6 files
- Give one clear next action at every stepin 19 of 307, across 8 files
- Understand product context and current state before recommendingin 15 of 307, across 3 files
- Limit guided tours to five dismissable stepsin 15 of 307, across 6 files
- Trace one request from entry to responsein 14 of 307, across 8 files
Said here and by no other author read
- Identify project root, package manager, and languages
- Read the smallest set of files needed
- Map major modules and their responsibilities
- Trace how data flows between modules
- Flag risky or complex areas
- Note runtime-defined behavior as limitations
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.