CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-hooks-builder

Scaffold hook packs, validate hooks.json schema, verify hook script permissions, migrate hook configuration, and troubleshoot Codex hook execution errors. Use when creating, auditing, upgrading, or validating Codex hook packs, hooks.json files, hook scripts, SubagentStart/SubagentStop lifecycle hooks, PreToolUse/PostToolUse/PreCompact hooks, Stop claim checks, or repo-local/user-level .codex hook installs.

75

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, actionable skill body with concrete commands, an explicit validation-gated workflow, and clean one-level-deep references. Minor conciseness redundancy and slightly thin inline examples keep it just short of perfect.

Suggestions

Dedupe the supported-event list (Workflow step 5 repeats events already named elsewhere) to tighten conciseness.

Fold the 'Examples' section's repair-loop items into the Workflow/Validation sections where they overlap, reducing restatement.

Inline one complete command-hook script example in the Hook Pack Example block so the core case is fully executable without opening references.

DimensionReasoningScore

Conciseness

Terse, directive prose that assumes Claude's competence and avoids explaining hooks/JSON/sandboxing basics, with minor redundancy (event lists repeated in Workflow step 5 and Examples restating Workflow) that could be trimmed.

4 / 5

Actionability

Provides concrete executable commands (rg/find with -perm -111, 'jq empty <hooks.json>', './bin/ask skills audit', 'plugin-eval analyze') and a real JSON hook example, with minor gaps where fuller examples are deferred to references.

4 / 5

Workflow Clarity

An 8-step sequenced workflow with explicit validation gates and feedback loops ('fix the first failed gate before continuing', 'stop at first failed gate; do not proceed until it is fixed and rerun') appropriate for a destructive code-execution skill.

5 / 5

Progressive Disclosure

A clear overview body with well-signaled, one-level-deep references (discovery-interview.md, hook-examples.md, contract.yaml, evals.yaml, task-profile.json) that are all real files, with detail appropriately split out.

5 / 5

Total

18

/

20

Passed

Description

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

A strong, third-person description that pairs concrete capabilities with an explicit 'Use when' trigger clause and rich, natural trigger terms including file extensions. It is comprehensive and highly distinguishable from other skills.

DimensionReasoningScore

Specificity

Lists five distinct concrete actions — 'Scaffold hook packs, validate hooks.json schema, verify hook script permissions, migrate hook configuration, and troubleshoot Codex hook execution errors' — giving comprehensive coverage with no gaps.

5 / 5

Completeness

Explicitly answers both 'what' (scaffold/validate/verify/migrate/troubleshoot) and 'when' via a concrete 'Use when creating, auditing, upgrading, or validating...' clause.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms with synonyms and file extensions: 'creating, auditing, upgrading, or validating', 'hooks.json files', 'repo-local/user-level .codex hook installs', plus specific event names users would name.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear Codex-hooks niche with distinct, specific triggers (lifecycle hooks, claim checks, .codex installs) and minimal overlap risk with other skills.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jscraik/Agent-Skills
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.