create-hook

Create or update Codex hooks for global or project scope by asking for scope and hook type when ambiguous, then writing the hook config, scripts, and any required feature flag config.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/create-hook/SKILL.md

Quality

Content

78%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 concise and actionable with a clearly sequenced workflow and verification step. Its main weakness is progressive disclosure: a reference file already exists for scope, events, and defaults, yet that content is inlined in the body rather than linked.

Suggestions

Replace the inlined scope paths, hook event list, and 'Practical defaults' with a pointer to references/hook-scope.md so the reference is signaled and duplication is removed.

Add an explicit feedback loop to step 7 (e.g. 'If verification fails, inspect the hook config/scripts, fix, and re-trigger').

Include a minimal example hook script (config block plus a tiny shell script) to lift actionability to copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet-driven with no padding or explanation of concepts Claude already knows; every line ('Prefer the smallest deterministic script', explicit file paths) earns its place.	5 / 5
Actionability	Provides concrete file paths, config keys ('[features] codex_hooks = true'), exit-code semantics, and event names, but lacks an example hook script body that would make guidance copy-paste ready.	4 / 5
Workflow Clarity	A clear 7-step sequence ends with an explicit 'Verify the result' checkpoint, but there is no validate->fix->retry feedback loop describing what to do when verification fails.	4 / 5
Progressive Disclosure	The body is well sectioned, but a reference file (references/hook-scope.md) exists whose scope/hook-event/default content is duplicated inline and never linked from the body, leaving the reference unsignaled.	3 / 5
	Total	16 / 20 Passed

Description

70%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 does and enumerating concrete artifacts it writes. It is held back by the absence of an explicit 'Use when...' trigger clause, capping completeness at 3.

Suggestions

Append an explicit trigger clause such as 'Use when the user wants to add or change Codex hooks (global or project-scoped).'

Mention common natural synonyms like 'automate', 'trigger on event', or 'hook into' to broaden trigger term coverage.

Optionally surface the supported hook events to make the capability scope concrete at a glance.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Create or update Codex hooks', 'writing the hook config, scripts, and any required feature flag config') with only minor gaps such as not enumerating the supported hook types.	4 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Captures the natural term 'Codex hooks' plus 'global or project scope' and 'hook type' that users would say, though a few common synonyms (e.g. 'automate', 'trigger') are absent.	4 / 5
Distinctiveness Conflict Risk	'Codex hooks for global or project scope' carves a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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: am-will/codex-skills
Path: skills/create-hook/SKILL.md
Commit: 9f954c3

Reviewed: 20 hours ago

Table of Contents

Discovery Implementation Validation

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.