nebi-maintenancelisted
Install: claude install-skill romanized/nebi-skill
# Maintenance: keep the doctrine honest
The active harness's core §0 override always wins. Masters live under `<repo-root>/claude-home/` and `<repo-root>/codex-home/`. Edit masters, not deployed home-directory copies. The source review and change record live at `<repo-root>/claude-home/nebi/SOURCES.md`.
## Refresh rules
- Discovery alone is read-only. An existing request to install, update, or integrate is authorization for that scope; do not ask for it again. Review fit before using it.
- Inspect third-party source, package metadata, and permissions before executing it. `npx`, `uvx`, installers, and even `--help` can fetch or run code; they are not read-only discovery. For an already reviewed, installed CLI, check current `--help` before relying on version-sensitive syntax.
- Filter hard. Prefer tightening or deleting an existing rule over adding another file. Keep each `SKILL.md` to the method that must load when it fires.
- Write for the stronger model: skip what it already does by default, skip fixed numbers and scenario lists unless they encode a measured threshold, prefer judgement to rigid rules, state the goal and constraints rather than every step, and prefer describing the interface over examples, which narrow what it tries. Conflicting or duplicated instructions cost thinking on every request; remove them.
- Give repeatable mechanics a script or helper, with its gotchas in the docstring, instead of prose steps. A guard that would be annoying always-on (blocking