CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hook-developer

Complete Claude Code hooks reference - input/output schemas, registration, testing patterns

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/hook-developer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable, Claude-Code-specific reference with complete schemas and copy-paste-ready code, but it is a monolithic ~725-line file with repeated warnings and no progressive disclosure into bundle files. The development workflow's steps and checkpoints exist but are scattered across topic-based sections rather than sequenced.

Suggestions

Split the per-event input/output schemas into a references/ file (e.g., references/events.md) and keep SKILL.md as an overview with the quick-reference table plus links, per progressive disclosure.

Add a numbered development workflow (1. write hook, 2. register in settings.json, 3. test with the echo command, 4. rebuild bundle if TypeScript, 5. run the debugging checklist) to make the sequence and checkpoints explicit.

Deduplicate repeated content: keep the 'tool_response not tool_result' warning, exit-code-2 behavior, and matcher patterns in one canonical place instead of three, and drop or merge the 'Key Learnings from Past Sessions' recap into the sections it duplicates.

DimensionReasoningScore

Conciseness

The body is dense and Claude-Code-specific (tables, schemas, code) with no padding about concepts Claude already knows, but it repeats material: 'tool_response not tool_result' appears three times (PostToolUse section, debugging checklist, Key Learnings), exit code 2 behavior is explained twice, matcher patterns appear in three places, and 'Key Learnings from Past Sessions' recaps earlier sections. Not 4 because these repetitions and the recap section should be trimmed.

3 / 5

Actionability

Fully executable throughout: complete JSON input/output schemas for every event, working Python/bash/TypeScript hook examples, exact manual test commands ('echo ... | .claude/hooks/my-hook.sh'), and a copy-paste esbuild bundle command. Not 4 because the examples are complete and cover the common cases (blocking, formatting, context injection, loop prevention).

5 / 5

Workflow Clarity

Validation assets exist (manual test commands, a debugging checklist, a rebuild-after-TS-edits step), but the development flow (write hook, register in settings.json, test manually, rebuild bundle) is never explicitly sequenced; the content is organized by topic rather than workflow, leaving checkpoints scattered and implicit. Not 4 because there is no ordered sequence tying the checkpoints together; not 2 because the checkpoints themselves are present.

3 / 5

Progressive Disclosure

No bundle files exist at all: roughly 500 lines of per-event API reference are inlined in SKILL.md where a references/ file (e.g., references/events.md) belongs, and 'See Also' points to non-bundle paths (/debug-hooks, .claude/rules/hooks.md). It stays at 3 rather than 2 because the file is well-sectioned with headers, tables, and a quick-reference summary that make it navigable; not 4 because the bulk reference detail is not split out.

3 / 5

Total

14

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, clearly stating what the skill contains (input/output schemas, registration, testing patterns) in concise third-person form. Its main weakness is the complete absence of 'when to use' trigger guidance, which caps completeness and limits natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when creating or debugging Claude Code hooks, registering hooks in settings.json, or working with hook events like PreToolUse, Stop, or SessionStart.'

Include natural trigger phrases users would actually say, such as event names (PreToolUse, PostToolUse, Stop), 'settings.json', and 'block a tool call', to improve trigger-term coverage.

Mention the hook's distinguishing capability (e.g., deciding what hooks can block vs. inject) to further reduce overlap with general Claude Code configuration skills.

DimensionReasoningScore

Specificity

The description names the domain ('Complete Claude Code hooks reference') and lists several concrete facets ('input/output schemas, registration, testing patterns'). It falls short of 5 because coverage has gaps (no mention of matchers, blocking behavior, or debugging), and exceeds 3 because it goes beyond 1-2 concrete actions.

4 / 5

Completeness

The 'what' is clear and concrete (a complete hooks reference covering schemas, registration, testing), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. Not 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

'hooks', 'Claude Code hooks', 'input/output schemas', 'registration', and 'testing' are terms users would naturally say when needing this skill. Not 5 because common variations are missing (event names like PreToolUse/Stop, 'settings.json', 'block a tool call').

4 / 5

Distinctiveness Conflict Risk

'Claude Code hooks' is a clear niche with distinct triggers, but 'registration' territory overlaps with general config/settings.json skills. Not 5 due to that minor overlap risk; not 3 because the niche is far more specific than a generic domain claim.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (730 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/hook-developer/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.