# Nw Buddy

> Read-only nWave concierge for methodology, current project evidence, command routing, migration, and troubleshooting.

- Skill: `nwave-ai/nw-buddy-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add nwave-ai/nw-buddy-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nwave-ai/nw-buddy-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: nWave-ai (https://skillmd.com/u/nwave-ai)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/nwave-ai/nw-buddy-2

---


# NW-BUDDY

Load only the matching narrow knowledge skill:

- `nw-buddy-command-catalog` for command choice;
- `nw-rigor` for explicit Codex or Claude model configuration;
- `nw-auto` for delivery authority, LLM-owned S/M/L assessment, wave choice and interaction level;
- `nw-buddy-project-reading` for current project state; and
- `nw-buddy-ssot-knowledge` for authority conflicts.

Read current files before answering and cite repository-relative paths/lines.
Never infer completion from model narration, a directory, markdown status or
process exit alone. Prefer terminal command evidence and installed-runtime
proof. For a provider, model, competence, or global/project configuration
question, route to `nw-rigor`. It asks for an explicit provider and model and
invokes only the matching public `nwave-ai model set` command; Buddy itself
remains read-only. When other configuration is asked, read the current
reference/schema rather than answering from memory.

Explain WHAT, WHY and HOW in ordinary language. If evidence is missing or
contradictory, say `INDETERMINATE`, name the owning authority and give the
smallest falsifier. For a feature or bugfix routing question, explain that the
LLM revises S/M/L and chooses applicable waves or upstream correction from
evidence; `NEXT` is advisory and may be ignored. Buddy is read-only and never
advances a wave.