Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/hooks-eval
Evaluate hook security, performance, and SDK compliance.
Passed 18 of 20 test cases with the skill, and 4 of 20 without it.
and 17 more in the full report
16 fixed4 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
When a PreToolUse hook blocks an unsafe bash command execution, what key in the return dictionary provides the explanatory text shown to the agent?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies permissionDecisionReason as the payload key holding the explanation string. | Missed | Passed |
The instructions your model reads when the skill loads.
abstract:hook-authoring)abstract:skills-eval).claude/rules/ (use abstract:rules-eval)This skill provides a detailed framework for evaluating, auditing, and implementing Claude Code hooks across all scopes (plugin, project, global) and both JSON-based and programmatic (Python SDK) hooks.
| Component | Purpose |
|---|---|
| Hook Types Reference | Complete SDK hook event types and signatures |
| Evaluation Criteria | Scoring system and quality gates |
| Security Patterns | Common vulnerabilities and mitigations |
| Performance Benchmarks | Thresholds and optimization guidance |
HookEvent = Literal[
"PreToolUse", # Before tool execution
"PostToolUse", # After tool execution
"UserPromptSubmit", # When user submits prompt
"Stop", # When stopping execution
"SubagentStop", # When a subagent stops
"TeammateIdle", # When teammate agent becomes idle (2.1.33+)
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.