statuslisted

# LLM Wiki — Status Confirm every piece of Layer 4 orchestration is wired and fires. Leave the vault exactly as you found it. This skill answers the question: "If I ran the pipeline right now, which hooks would fire and which would silently skip?" ## When to invoke - Immediately after installing the plugin — verify the install. - After editing hooks or scripts — verify the edit. - When the user suspects a hook is not firing (e.g., frontmatter violations slip through). - Periodically, as a smoke test. ## Reading contract - `hooks/hooks.json` — the hook wiring manifest. - Every script referenced from `hooks/hooks.json` — confirm executable, valid shell, returns expected exit codes for synthetic inputs. - `vault/CLAUDE.md` — the schema, to construct valid and invalid test payloads. - The user's project tree — only to determine the vault path; never its contents. ## Writing contract Zero writes to `vault/`. Specifically: - No log append (this skill is a diagnostic; logging health checks clutters the log). - No scratch files under `vault/`. - Transient test payloads may be constructed in a tempdir outside `vault/` (e.g., `$TMPDIR`) and must be removed before the skill returns. The skill enforces its own non-mutation invariant: compare `git status vault/` (or a checksum of `vault/`) before and after; any diff is a skill bug and must be surfaced as a FAIL. ## Workflow Run these checks in order. Each produces one line in the report. 1. **Dependency check.** `