Agent skill · AI & Agents

nw-buddy-project-reading

How the nWave buddy agent reads a project to answer questions — detection, order of inspection, and citation discipline.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill nw-buddy-project-reading --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/agent/nw-buddy-project-reading/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Project Reading for the Buddy Agent The buddy agent answers questions about a project by *reading it*, not by guessing. Every answer must be traceable to a specific file and line. This skill is the reading protocol. ## Goals 1. Understand the project's architecture, current state, and methodology enough to answer the user's question. 2. Cite every claim (`path:line`) so the user can verify. 3. Avoid reading more than necessary — tokens and time both cost. 4. Never invent file contents, function names, or architecture claims. ## Order of inspection (cheap first) Read in this order. Stop as soon as you have enough context for the current question. ### 1. Project identity (always, <1s) - `README.md` — what is this project, for whom. - `CLAUDE.md` (project root) — how Claude-based tools should behave here. - `pyproject.toml` / `package.json` / `Cargo.toml` / equivalent — language, dependencies, versions, scripts. - `VERSION` or the version field in the package manifest. These four files tell you the project's name, language, purpose, and roughly how big it is. Skip nothing here. ### 2. Planning and state - `BACKLOG.md` — the single source of truth for planned work (in nWave projects)

What's inside
Steps it walks through
  1. Goals
  2. Order of inspection (cheap first)
  3. 1. Project identity (always, <1s)
  4. 2. Planning and state
  5. 3. Architecture documentation
  6. 4. Source layout
  7. 5. Tests
  8. 6. Specific files (on demand)
  9. Detection heuristics
  10. Wave progress detection
  11. Citation discipline
  12. What NOT to do
  13. Escalation
  14. Example: "what is this project and where are we with it?"
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the nw-buddy-project-reading skill do?

How the nWave buddy agent reads a project to answer questions — detection, order of inspection, and citation discipline.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill nw-buddy-project-reading --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going