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.
Install with Tessl CLI
npx tessl i github:anthropics/claude-plugins-official --skill writing-hookify-rulesOverall
score
74%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
63%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 excels at trigger terms and distinctiveness due to the specific 'hookify' terminology, but fails to explain what hookify actually is or what concrete actions the skill enables. Someone unfamiliar with hookify would have no idea what this skill does beyond generic 'rule creation' and 'guidance'.
Suggestions
Add a clear explanation of what hookify is and what hookify rules accomplish (e.g., 'Hookify rules define automated actions triggered by specific events...')
List specific concrete capabilities like 'create conditional rules, define trigger patterns, configure rule actions, validate rule syntax'
Restructure to lead with 'what it does' before the 'Use when...' clause for better clarity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions - it only mentions 'create', 'write', 'configure', 'add' rules and 'guidance on syntax and patterns' without explaining what hookify rules actually do or what specific capabilities the skill provides. | 1 / 3 |
Completeness | The description clearly answers 'when' with explicit trigger phrases, but the 'what' is very weak - it doesn't explain what hookify is, what rules do, or what concrete capabilities the skill provides beyond vague 'guidance'. | 2 / 3 |
Trigger Term Quality | Good coverage of natural trigger terms users would say: 'create a hookify rule', 'write a hook rule', 'configure hookify', 'add a hookify rule', 'hookify rule syntax'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The term 'hookify' is highly specific and distinctive. It's unlikely to conflict with other skills since it targets a specific tool/system with unique terminology. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent concrete examples and good organization. The main weaknesses are verbosity (explaining regex basics Claude knows, some redundancy between sections) and missing validation steps for testing rules work correctly. The quick reference section is helpful but duplicates earlier content.
Suggestions
Remove or significantly condense the 'Regex Basics' section - Claude knows regex syntax; keep only hookify-specific escaping notes for YAML
Add a validation step to the workflow: 'Test the rule triggers correctly by running a command/edit that should match, then verify the warning appears'
Consolidate the quick reference with earlier content to reduce duplication - either remove it or make earlier sections reference it instead of duplicating
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (regex basics Claude knows, repeated pattern examples). The quick reference at the end duplicates earlier content. Could be tightened by 30-40%. | 2 / 3 |
Actionability | Excellent concrete examples throughout with copy-paste ready YAML/markdown snippets. Every concept is illustrated with executable rule definitions and specific regex patterns. | 3 / 3 |
Workflow Clarity | The workflow section provides clear steps for creating/refining/disabling rules, but lacks validation checkpoints. No guidance on testing that a rule actually triggers correctly before relying on it. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from basic to advanced. References external examples directory appropriately. Content is logically structured with a useful quick reference summary. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
91%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 | |
- 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.