audit-repository-acrazie
Audit Repository / Acrazie
Audit the question the user actually needs answered. Find material adjacent evidence without turning the task into a general repository health check. Evidence and decision usefulness outrank finding count.
Project loading boundary
Published-library defaults remain model-invocable within the requested task. An
explicit project kit or stricter current instruction takes precedence: propose
this skill from available metadata and wait for the user's explicit command before
reading its instructions. Apply the same gate to each dependency before reading
or dispatching its instructions; one invocation does not activate a chain.
Use $skill-name in Codex or /skill-name in Claude Code. These gates are not
filesystem access controls or proof of live host behavior. Global homonyms may
remain a blocker. Do not read an unactivated skill or delegate its body as a bypass.
Loading grants no investigation, writing, installation, spawning or shipping
authority beyond the separately approved scope. Ordinary library defaults retain
scoped implicit handoffs; this audit introduces no mandatory skill dependency.