CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hooks

Hook Development Rules

Quality

60%

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/hooks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

The body is an efficient, well-organized reference of executable templates for building hooks, with a clear implicit workflow and a manual testing step. Its main weaknesses are the placeholder-laden TypeScript handler template and the absence of error-recovery guidance when a test fails or a hook's output is malformed.

Suggestions

Make the TypeScript template fully executable by defining the readStdin() helper (e.g. a small snippet that reads stdin to a string) so the handler pattern is copy-paste ready.

Add a short error-recovery note to the Testing section: what to check when a hook produces no output or invalid JSON (exit codes, stderr, npx tsx failures), forming a validate-then-fix feedback loop.

Include one complete worked example (e.g. a filled-in PreToolUse handler with a real HookInput shape) so the event-specific field structure is concrete rather than implied.

DimensionReasoningScore

Conciseness

The body is lean and template-driven — shell/TypeScript/JSON examples plus a terse event list — with no explanation of concepts Claude already knows and no padding. Re-checked against anchor 4 (minor over-explanation to trim): none found, so anchor 5 (every token earns its place) is the best fit.

5 / 5

Actionability

The shell wrapper ("cat | npx tsx <handler>.ts"), the test command, and the registration JSON are concrete and near copy-paste ready, but the TypeScript handler is a skeleton with placeholders (undefined readStdin(), "// Process input", "EventName"). That places it at anchor 4 (mostly executable, minor gaps) rather than anchor 5 (fully copy-paste ready) or anchor 3 (pseudocode-level guidance).

4 / 5

Workflow Clarity

The skill lays out a coherent sequence — write the shell wrapper, implement the TypeScript handler, register in settings.json, then test with the echo command — and includes an explicit verification step ("Test hooks manually"). It is not a destructive/batch operation so the validation cap does not apply; it falls short of anchor 5 only because there is no error-recovery feedback loop (e.g. what to do when the test fails or a hook's output is malformed).

4 / 5

Progressive Disclosure

This is a compact (~65-line), single-file skill with no bundle files (references/, scripts/, and assets/ do not exist), and its sections are clearly headed (Pattern, Templates, Events, Testing, Registration) with nothing that needs splitting out. Per the simple-skill guidance this matches anchor 5 (well-organized sections, no external references needed); anchor 4 would require organization gaps, and none are present.

5 / 5

Total

18

/

20

Passed

Description

20%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 a bare title rather than a capability description: it names the hook-development domain but includes no actions, no trigger guidance, and no use-when clause. Neither Claude nor a user could tell what the skill does or when to invoke it, so it would rarely be selected correctly.

Suggestions

Rewrite the description as a third-person capability sentence, e.g. "Develops Claude Code hooks using a shell wrapper that invokes a TypeScript handler via npx tsx; covers writing handlers, registering hooks in .claude/settings.json, and manual testing."

Add an explicit "Use when..." clause naming concrete triggers: creating or editing files in .claude/hooks/, adding hooks to settings.json, wiring PreToolUse/PostToolUse/Stop events, or when the user mentions hook wrappers or hook handlers.

Include natural trigger terms and synonyms (hooks, hook events, PreToolUse, settings.json, shell wrapper, tsx) to improve both completeness and distinctiveness versus git hooks/webhooks.

DimensionReasoningScore

Specificity

"Hook Development Rules" names the domain but contains no verbs or concrete actions, sitting between anchor 1 (no concrete actions) and anchor 2 (domain named, minimal actions). It does not reach anchor 3, which requires 1-2 concrete actions such as "Processes PDF files and extracts content".

2 / 5

Completeness

It answers neither "what does this do" (it is a title label, not a capability statement) nor "when should Claude use it" — there is no 'Use when...' clause or equivalent trigger guidance. This matches anchor 1 (missing both what and when) and cannot reach anchor 2, which requires at least a vague 'what' or a 'when'.

1 / 5

Trigger Term Quality

Only one relevant keyword ("hook") is present; natural phrases users would actually say — "add a hook", "PreToolUse", "settings.json", "shell wrapper" — are missing. This matches anchor 2 (one or two generic keywords, missing natural phrases) rather than anchor 3's somewhat broader keyword coverage.

2 / 5

Distinctiveness Conflict Risk

"Hook" is somewhat specific but the term overlaps with git hooks and webhooks, so it could trigger for the wrong skill. This matches anchor 3 (somewhat specific, residual overlap risk) rather than anchor 4, which requires near-distinct triggers.

3 / 5

Total

8

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/hooks/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.