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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is tdg-personal/hookify-rules

Quality

Content

76%Weight 40%Scale 1-5

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

A well-structured, highly actionable reference for authoring hookify rules with copy-paste templates and complete field/operator coverage. Its main gap is the absence of an explicit end-to-end rule-creation workflow with validation checkpoints, and minor over-explanation of basic regex.

Suggestions

Add a short numbered 'Creating a rule' workflow: 1) identify the event/pattern from the request, 2) draft frontmatter, 3) validate the regex with the python3 test command, 4) write the file to .claude/hookify.{name}.local.md and confirm it loads via /hookify-list.

Trim or collapse the 'Regex Basics' section (\s/\d/\w/+/*/?/|) since Claude already knows these; keep only the hookify-specific pitfalls and the YAML-escaping note.

Consider moving the detailed Event Type Guide and Pattern Writing Tips into a separate reference file (e.g. PATTERNS.md) linked from SKILL.md, keeping the main file a lean overview with the format spec and quick reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight tables and complete code blocks, but the 'Regex Basics' section explains tokens Claude already knows ('\s whitespace, \d digit, \w word char') — minor over-explanation that could be trimmed.	4 / 5
Actionability	Provides fully copy-paste-ready rule templates (basic and multi-condition formats), a complete frontmatter field table, enumerated operators, per-event condition fields, and an executable test command, covering the common rule-authoring cases.	5 / 5
Workflow Clarity	This is a reference guide rather than a sequenced process; a testing checkpoint exists ('python3 -c "import re; ..."') but there is no explicit create -> test -> install/verify workflow, and the skill exceeds the 50-line simple-skill exception.	3 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references, but everything is inlined in a single >50-line file; the detailed event-type/pattern reference could be split into a one-level-deep reference file.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 strong, third-person description that explicitly pairs capability statements with a 'Use when...' trigger clause and targets a distinct, low-conflict niche. Its only weakness is mild redundancy among the action verbs and a few missing trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('create a hookify rule, write a hook rule, configure hookify, add a hookify rule') plus 'guidance on hookify rule syntax and patterns', but create/write/add are near-synonyms rather than distinct capabilities, leaving minor coverage gaps.	4 / 5
Completeness	Clearly states both what the skill does (create/write/configure hookify rules, syntax guidance) and when to use it via the explicit 'This skill should be used when the user asks to...' trigger clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrasings ('create a hookify rule', 'configure hookify', 'write a hook rule') with good synonym coverage, but omits file-extension/asset triggers and a few common variations, stopping short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The 'hookify' niche is specific and named, with distinct triggers ('hookify rule', 'configure hookify') that are unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: skills/hookify-rules/SKILL.md
Commit: 06c5e11

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.