writing-hookify-rules
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
63
43%
Does it follow best practices?
Impact
100%
2.38xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/hookify/skills/writing-rules/SKILL.mdQuality
Discovery
37%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is heavily skewed toward trigger terms and 'when to use' guidance while completely neglecting to explain what the skill actually does. It reads as a list of activation phrases rather than a meaningful description of capabilities. A reader unfamiliar with 'hookify' would have no idea what this skill produces or what domain it operates in.
Suggestions
Add a clear 'what' clause explaining what hookify rules are and what the skill produces (e.g., 'Creates hookify rules that [specific purpose/function]. Generates YAML/JSON configuration files for...').
Describe 2-3 concrete actions the skill performs, such as generating rule files, validating syntax, or configuring specific hook behaviors.
Briefly explain the domain or context of hookify so Claude can distinguish this skill from other configuration or rule-writing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not describe any concrete actions or capabilities. It only mentions trigger phrases like 'create a hookify rule' and 'configure hookify' but never explains what hookify rules are, what they do, or what specific actions the skill performs. | 1 / 3 |
Completeness | The description answers 'when' (with explicit trigger phrases) but completely fails to answer 'what does this do'. There is no explanation of what hookify is, what the skill produces, or what capabilities it provides. The 'what' is essentially missing. | 1 / 3 |
Trigger Term Quality | The description includes multiple natural trigger phrases users would say: 'create a hookify rule', 'write a hook rule', 'configure hookify', 'add a hookify rule', and 'hookify rule syntax and patterns'. These are specific and varied. | 3 / 3 |
Distinctiveness Conflict Risk | The term 'hookify' is fairly distinctive and unlikely to conflict with generic skills, but without explaining what hookify actually does, it's unclear how it differs from other configuration or rule-writing skills. The niche is named but not defined. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, concrete guidance for writing hookify rules with excellent copy-paste ready examples covering all event types and conditions. However, it is significantly bloated by unnecessary regex tutorials and pattern-writing tips that Claude already knows, and the monolithic structure would benefit from splitting reference material into separate files. The workflow section lacks validation checkpoints for confirming rules work as intended.
Suggestions
Remove the entire 'Regex Basics' and 'Pattern Writing Tips' sections — Claude already knows regex syntax. Keep only the hookify-specific pattern examples.
Add a validation step to the workflow: e.g., 'After creating the rule, trigger the matching tool use and verify the hookify message appears in the output.'
Split the event type guide and common patterns into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the basic structure, one example, and links to details.
Remove the 'Common Pitfalls' section or reduce it to a single line noting to use unquoted YAML patterns to avoid escaping issues.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at 200+ lines. It explains regex basics (\s, \d, \w, metacharacters, escaping) that Claude already knows, includes a 'Regex Basics' tutorial section, explains what kebab-case is by example, and repeats the same rule structure multiple times across sections. The 'Pattern Writing Tips' and 'Common Pitfalls' sections add significant token cost for concepts Claude is already expert in. | 1 / 3 |
Actionability | The skill provides fully concrete, copy-paste ready markdown rule templates with complete YAML frontmatter and message bodies. Every event type has a working example, the conditions syntax is fully specified with all field/operator options, and the file naming convention is explicit. | 3 / 3 |
Workflow Clarity | The 'Creating a Rule' and 'Refining a Rule' workflows are listed as clear steps, but there are no validation checkpoints — no way to verify a rule is syntactically correct, no feedback loop for testing that a pattern actually matches intended inputs, and the 'Test immediately' step is vague without specifying how to confirm the rule triggered. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, and references examples in `${CLAUDE_PLUGIN_ROOT}/examples/`. However, the document is monolithic — the regex tutorial, common patterns catalog, and event type guide could all be separate reference files. The inline content is far too long for a SKILL.md overview, with no bundle files to offload to. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- anthropics/claude-plugins-official
- Commit
76b35e9
- 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.