Design a deterministic blocking gate for a repeated unsafe or invalid transition after advisory guidance has failed.
Use when the operator asks to enforce a state transition, prevent a destructive or secret-bearing action, or convert a proven verification rule into a runtime guard.
Do not assume Claude hook events or invent a hook surface; confirm the current runtime's supported mechanism first.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeDeclared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars9
Default branchmain
Open issues0
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Declared agentsclaude-code
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md1,548 B
docsSUMMARY.md417 B
History
First seen on skills.sh
First recorded snapshot · 11 installs
SKILL.md
Enforcement
Enforcement converts one already-proven invariant into a blocking control.
Procedure
Identify the repeated invalid action and the existing deterministic assertion that detects it.
Confirm the actual runtime owner: repository script, CI gate, Codex rule, plugin hook, operating-system sandbox, or external service policy.
Place the block at the narrowest point before irreversible state change.
Fail closed only for destructive, secret, security, or external-send boundaries. Keep ordinary routing and quality guidance informational unless the repository explicitly requires a block.
Test an allowed case, a denied case, diagnostic output, and recovery after the condition is corrected.
Document how to disable or remove the guard safely.
Boundary
determinism owns the machine-checkable assertion.
enforcement owns where and how that proven assertion blocks an action.
verify reports readiness but does not create blocking runtime policy.
Runtime-specific hook schemas belong in the plugin or repository that implements them, not in this global skill.