Enable
Activate Crucible enforcement in the current project. Use this when you intentionally want Crucible's hooks (PreToolUse, PostToolUse, Stop) to enforce evidence-gated completion. Without activation, Crucible is silent in this project. This is the explicit opt-in step before starting any /crucible:planning or /crucible:validation workflow. Creates a sentinel file at .crucible/active in the project root. Reversible via /crucible:disable. Safe to invoke multiple times — idempotent.From its SKILL.md
npx -y skills add krzemienski/crucible --skill enableAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, as published. Nobody here has run it
Crucible — Enable enforcement in this project
Purpose
Activate Crucible's gate-enforcement hooks in the current working directory. Without this, the hooks are silent no-ops (so user-scope plugin installs do not break unrelated projects).
Workflow
- Verify
${CLAUDE_PROJECT_DIR}is the project root (not a subdirectory). - Create the directory and sentinel file via Bash:
mkdir -p ${CLAUDE_PROJECT_DIR}/.crucible touch ${CLAUDE_PROJECT_DIR}/.crucible/active - If
${CLAUDE_PROJECT_DIR}/.crucible/disabledexists, remove it (kill-switch override would otherwise still suppress enforcement):rm -f ${CLAUDE_PROJECT_DIR}/.crucible/disabled - Confirm to the user with a one-line message including the absolute path:
Crucible enabled at <project>/.crucible/active. Hooks will now enforce.
Forbidden actions
- Do NOT create
.crucible/activeoutside the project root. - Do NOT auto-create
evidence/content; the user (or other Crucible skills) does that. - Do NOT silently re-enable if
.crucible/disabledis present without telling the user.
Example
User: /crucible:enable
Assistant: Crucible enabled at /Users/me/myproject/.crucible/active.
Pre/Post/Stop hooks will now enforce gate semantics in this project.
To opt out later: /crucible:disable
Iron Rule
Activation is the only thing this skill does. It does not run the gate. It does not generate evidence. It does not rewrite report.json. It is a 2-line idempotent operation that flips this project from "Crucible is invisible" to "Crucible enforces".