CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/hookify-rules/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is highly actionable and well-organized with executable examples and a genuine validation step, but minor redundancy and re-taught regex basics slightly reduce token efficiency, and the rule-creation process lacks an explicit sequenced workflow.

Suggestions

Remove the 'Quick Reference' section (or trim 'Regex Basics') since both duplicate content already covered above, to tighten token efficiency.

Add a short numbered 'Creating a rule' workflow that sequences choose-event → write-pattern → test-with-the-python-one-liner → place-in-.claude, weaving the existing test command in as an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient and reference-style, but the 'Quick Reference' minimum-viable-rule repeats the 'Basic Structure' example and 'Regex Basics' re-teaches tokens Claude already knows, pulling it below the lean score-3 anchor.

2 / 3

Actionability

Provides complete, copy-paste-ready rule examples (basic and multi-condition), a concrete frontmatter field table, specific regex patterns, and an executable test command, matching the score-3 anchor.

3 / 3

Workflow Clarity

A validation checkpoint exists in the 'Testing' section, but rule creation is organized by topic rather than as a sequenced process with explicit checkpoints, fitting the score-2 anchor of present-but-implicit checkpoints.

2 / 3

Progressive Disclosure

The skill is self-contained with no (and no need for) external bundle files, and is organized into clear single-level sections with no nested references, matching the well-organized score-3 anchor for a self-contained skill.

3 / 3

Total

10

/

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.

The description uses strong, natural trigger phrasing and a distinctive niche, but frames the skill mostly as a list of user requests rather than a crisp statement of what it does, leaving the 'what' side underdeveloped.

Suggestions

Lead with a concise statement of what the skill does (e.g., 'Creates and configures hookify rules — markdown files that trigger contextual messages on bash, file, stop, or prompt events.'), then keep the 'Use when...' trigger clause.

Compress the repetitive 'hookify rule' variants into a tighter trigger list to reduce verbosity without losing natural keywords.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('create a hookify rule, write a hook rule, configure hookify, add a hookify rule') rather than vague language, matching the score-3 anchor of multiple specific actions.

3 / 3

Completeness

The explicit 'when' trigger is present and strong, but the 'what' is thin — it enumerates user requests rather than stating the skill's function, so it does not clearly answer both what and what well enough for a 3.

2 / 3

Trigger Term Quality

Covers natural phrasings a user would say ('create a hookify rule', 'write a hook rule', 'configure hookify') with good variation, fitting the score-3 anchor despite heavy reuse of the 'hookify rule' phrase.

3 / 3

Distinctiveness Conflict Risk

'hookify' is a distinctive proper noun with rule-specific triggers, making it unlikely to fire for the wrong skill and matching the clear-niche score-3 anchor.

3 / 3

Total

11

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
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.