tdg-personal/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.
56
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
29%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 imbalanced: it provides only 'when to use' guidance with decent trigger terms for the niche domain of hookify, but completely omits what the skill actually does. Without any concrete capability descriptions, Claude cannot make an informed decision about whether this skill is appropriate beyond keyword matching on 'hookify'.
Suggestions
Add a clear 'what it does' section listing specific capabilities, e.g., 'Generates hookify rule configurations, validates rule syntax, and provides templates for common hook patterns.'
Include concrete output formats or artifacts the skill produces (e.g., 'Creates YAML/JSON rule definitions for hookify') to improve specificity.
Restructure to lead with capabilities followed by a 'Use when...' clause, e.g., 'Generates and validates hookify rule configurations with proper syntax. Use when the user asks to create, write, or configure hookify rules.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions no concrete actions—it only says when to use the skill ('create a hookify rule', 'write a hook rule') but never describes what the skill actually does (e.g., generates YAML config, validates rule syntax, etc.). The capabilities are entirely absent. | 1 / 3 |
Completeness | The description answers 'when' (when the user asks to create/write/configure hookify rules) but completely fails to answer 'what does this do'—there is no explanation of the skill's capabilities, outputs, or concrete actions it performs. | 1 / 3 |
Trigger Term Quality | It includes several natural trigger terms like 'hookify rule', 'hook rule', 'configure hookify', and 'hookify rule syntax', which are relevant keywords a user might say. However, it lacks variations or broader context terms (e.g., file types, specific rule types, related concepts) that would improve coverage. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'hookify' is highly specific and niche, making it very unlikely to conflict with other skills. The triggers are clearly scoped to hookify rule creation and configuration. | 3 / 3 |
Total | 7 / 12 Passed |
Implementation
64%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 reference skill for hookify rule creation with excellent actionability through concrete examples and copy-paste ready templates. Its main weaknesses are including regex basics Claude already knows, and lacking an explicit workflow for creating and validating rules end-to-end. The content would benefit from trimming known concepts and adding a brief create-test-verify workflow.
Suggestions
Remove the 'Regex Basics' subsection entirely — Claude knows regex syntax. Keep only the 'Common Pitfalls' which are hookify-specific.
Add a brief numbered workflow at the top: 1. Create rule file 2. Write frontmatter + message 3. Test pattern with the python one-liner 4. Verify rule appears in `/hookify-list`.
Consider moving the 'Advanced Format (Multiple Conditions)' and 'Event Type Guide' sections to a separate HOOKIFY-REFERENCE.md file, keeping SKILL.md focused on the quick-start pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but some sections like 'Regex Basics' explain concepts Claude already knows well (regex syntax). The pattern writing tips section could be trimmed significantly. | 2 / 3 |
Actionability | Provides complete, copy-paste ready rule templates in proper markdown format, a concrete testing command, specific file naming conventions, and a minimum viable rule example. The conditions table with operators and fields is highly actionable. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/syntax guide rather than a multi-step workflow, but it lacks any validation step for verifying a rule works after creation. There's no feedback loop like 'create rule → test it → verify it triggers → adjust pattern if needed'. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and headers, but it's somewhat long for a single file. The event type guide, pattern tips, and advanced conditions could be split into separate reference files. The commands section references /hookify-help for 'full documentation' which is good but the inline content is borderline too detailed. | 2 / 3 |
Total | 9 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents