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.mdFile naming, location, and rule structure
Correct directory
0%
100%
Correct file naming prefix
0%
100%
Correct .local suffix
0%
100%
Descriptive file names
100%
100%
Name field kebab-case
50%
100%
Name field starts with verb
0%
100%
Correct event type
0%
100%
enabled field present
0%
100%
Message explains detection
100%
100%
Message explains why
100%
100%
Message suggests alternatives
100%
100%
Gitignore updated
0%
100%
Multi-condition rules and pattern quality
Multi-condition for TS rule
100%
100%
file_path field used
100%
100%
new_text field used
100%
100%
Valid operator used
100%
100%
console.log pattern specificity
100%
100%
eval pattern specificity
100%
100%
Unquoted YAML patterns
100%
100%
Correct event type
100%
100%
Pattern test script present
100%
100%
Correct file naming
100%
100%
Name field starts with verb
0%
100%
Stop/prompt events and action field usage
Stop event used
0%
100%
Prompt event used
0%
100%
warn action for stop rule
0%
100%
block action for prompt rule
0%
100%
user_prompt field in prompt rule
0%
100%
Prompt rule uses conditions array
0%
100%
Stop rule message is checklist
25%
100%
Correct file naming
0%
100%
Name field starts with verb
0%
100%
enabled field present
0%
100%
Gitignore updated
0%
100%
48aa435
Table of Contents
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.