Agent skill

nw-buddy-ssot-knowledge

Single Source of Truth detection — where truth lives in an nWave repo and how to avoid contradicting it.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill nw-buddy-ssot-knowledge --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-ssot-knowledge/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

# SSOT Knowledge for the Buddy Agent Large projects accumulate multiple copies of "the same" information: a version in `pyproject.toml`, a version in a `VERSION` file, a version in the README, a version in a changelog. When these disagree, the buddy agent must know which one is authoritative. This skill is the SSOT map for nWave projects. ## Why it matters Answering a user's question with a stale secondary copy is worse than saying "I don't know": it spreads wrong information with a confident tone. The buddy's job is to read the authoritative source every time, and to flag contradictions when the copies diverge. ## The SSOT map Each concept below has one authoritative file. Read that file first. Treat everything else as a cache that may be stale. ### Versions - **Authoritative**: `pyproject.toml` `[project] version = "..."` (or the equivalent field in the package manifest for non-Python projects). - **Caches**: `VERSION` file, README badges, docs footer, release notes. - **Rule**: quote `pyproject.toml`. If asked about a cache that disagrees, report the discrepancy. ### Planned work - **Authoritative**: `BACKLOG.md` at the repo root. - **Caches**: GitHub issues, conversation contex

What's inside
Steps it walks through
  1. Why it matters
  2. The SSOT map
  3. Versions
  4. Planned work
  5. Architecture intent
  6. Runtime behavior
  7. Configuration
  8. Agent / command definitions
  9. Git state
  10. Conflict resolution hierarchy
  11. How to recognize a stale secondary copy
  12. Read-before-answer discipline
  13. Never invent, always cite
  14. A short example
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the nw-buddy-ssot-knowledge skill do?

Single Source of Truth detection — where truth lives in an nWave repo and how to avoid contradicting it.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill nw-buddy-ssot-knowledge --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