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.

2.38x

Quality

—

Does it follow best practices?

Impact

100%

2.38x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

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

A highly actionable, well-structured guide with concrete copy-paste rule templates, weakened by a regex tutorial Claude does not need, an implicit validation loop, and a monolithic layout that keeps reference material inline rather than in bundled files.

Suggestions

Remove or collapse the "Regex Basics" tutorial (metacharacters \s, \d, \w, +, *, ?, |) and the redundant closing "Quick Reference" that restates event types, fields, and operators — Claude already knows regex, so keep only hookify-specific guidance.

Turn the rule-creation workflow into an explicit validate→fix→retest loop: after "Test immediately", add a checkpoint like "If the rule does not trigger as expected, adjust the pattern and re-test before relying on it."

Move the detailed event-type guides, operator/field reference, and common-pattern lists into bundled reference files (e.g. references/event-types.md, references/pattern-catalog.md) linked from a concise overview, so SKILL.md stays a lean entry point.

Dimension	Reasoning	Score
Conciseness	Most content is hookify-specific and useful, but the "Regex Basics" section explains metacharacters (\s, \d, \w, +, *, ?, \|) Claude already knows, and the closing "Quick Reference" rehashes event types, fields, and operators already covered — tightening opportunities that keep it off the lean score-3 level.	2 / 3
Actionability	Provides complete, copy-paste-ready rule-file templates with frontmatter and message bodies, concrete per-event examples, a working test command (python3 -c "import re; ..."), and specific good/bad naming patterns — fully executable guidance rather than pseudocode.	3 / 3
Workflow Clarity	The Workflow section gives clearly numbered sequences for creating/refining/disabling rules and mentions testing, but validation checkpoints are implicit ("test immediately - rules are read dynamically") with no explicit fix→retest feedback loop, matching the score-2 anchor of steps present but checkpoints missing or implicit.	2 / 3
Progressive Disclosure	Sections are well-organized and the Examples reference is clearly signaled one level deep, but the ~370-line body is monolithic with regex and event-type reference material inline and no bundle files splitting content out, so it does not meet the score-3 bar of content appropriately split across files.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 trigger-rich, distinctive description that captures natural user phrasings well, but it states when-to-use without an explicit capability statement, leaving the "what" implied. Adding a concise active-voice capability clause would lift completeness to the top level.

Dimension	Reasoning	Score
Specificity	Quotes several concrete actions in the hookify domain — "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", plus "guidance on hookify rule syntax and patterns" — exceeding the score-2 anchor that names only a domain and a couple of actions.	3 / 3
Completeness	The "when" is explicit ("when the user asks to..."), but the "what" is only implied through trigger phrases — there is no explicit capability statement such as "Creates and writes hookify rules" — so it does not clearly answer both what and when as the score-3 anchor requires.	2 / 3
Trigger Term Quality	Embeds literal quoted user utterances ("create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule") plus "hookify rule syntax and patterns", giving strong coverage of natural phrasings a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The term "hookify" is highly distinctive and the description is entirely scoped to hookify rules with niche-specific triggers, making conflict with other skills unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: anthropics/claude-plugins-official
Commit: 30a213f

Reviewed: 3 days 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.