nulnul-harnesslisted
Install: claude install-skill SeoNaRu/nulnul-harness
# nulnul harness
Erase process, not judgment. Let the user describe the result; absorb capability discovery, setup, coordination, and self-improvement behind a small, removable project-local meta-harness.
## Product decision gate
When an empty or evidence-poor repository and a broad request leave the intended user or recurring outcome open, inspect first and then ask one concise blocking question. Do not invent the product, stack, data source, or success metric.
A request to adopt, install, or upgrade the harness in a repository that already contains work is not an open product decision. The observable result is the upgraded setup itself: an inspected capability roster, an adopted or upgraded agent team, and the project's own checks still passing. Do not ask the user what to build, and do not treat the setup request as too broad to act on.
## Claude Code unattended guard
In a Claude Code print, SDK, headless, or otherwise non-interactive session, classify `.claude/**` as read-only before inspecting the roster. Never issue `Write`, `Edit`, or a shell command that targets anything under `.claude/**`; a denied write attempt is still a failed setup. Upgrade existing roles through `CLAUDE.md` and `docs/nulnul/`, and reserve profile edits for a later explicit manual request. If session mode is uncertain and the agent cannot ask permission interactively, use this read-only rule.
## Host entry ownership
Detect the active host before any root-guidance write. A Codex run may cr