hook-factory
Generate production-ready Claude Code hooks with interactive Q&A, automated installation, and enhanced validation. Supports 10 templates across 7 event types for comprehensive workflow automation.
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-code-skill-factory --skill hook-factory56
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
32%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 identifies a specific domain (Claude Code hooks) and mentions some capabilities, but relies on marketing language ('production-ready', 'comprehensive') rather than concrete actions. The critical weakness is the complete absence of a 'Use when...' clause, making it difficult for Claude to know when to select this skill from a large skill library.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'hook', 'pre-commit', 'post-response', 'Claude Code automation', or 'event handler'
Replace vague terms like 'comprehensive workflow automation' with specific examples of what the 7 event types are (e.g., 'PreToolUse, PostToolUse, Notification events')
List 2-3 concrete template examples instead of just stating '10 templates' (e.g., 'lint-on-save hooks, auto-format hooks, security validation hooks')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Claude Code hooks) and mentions some actions (interactive Q&A, automated installation, validation), but 'production-ready' and 'comprehensive workflow automation' are vague marketing terms. The '10 templates across 7 event types' adds some specificity but doesn't explain what those templates or events actually are. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. There's no indication of when Claude should select this skill over others. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also partially vague, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'hooks' and 'Claude Code hooks' which are relevant, but misses natural user phrases like 'hook template', 'pre-commit', 'post-response', or specific event type names users might mention. 'Workflow automation' is somewhat generic. | 2 / 3 |
Distinctiveness Conflict Risk | 'Claude Code hooks' is fairly specific and unlikely to conflict with generic automation skills, but 'workflow automation' and 'validation' could overlap with other skills. The lack of explicit triggers increases conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable guidance with clear workflows and validation checkpoints, but is severely bloated with unnecessary verbosity. The content repeats itself extensively (features listed 3+ times), includes marketing language, and embeds content that belongs in referenced files. A 400+ line SKILL.md for a hook generator violates token efficiency principles.
Suggestions
Reduce to ~100 lines by removing repeated feature lists, marketing language ('NEW!', 'Key Features'), and content Claude already knows (what hooks are, basic JSON structure)
Move troubleshooting, version history, and detailed architecture diagrams to separate referenced files (TROUBLESHOOTING.md, ARCHITECTURE.md)
Consolidate the three 'Example Interactions' into a single table or compact format instead of verbose prose blocks
Remove explanatory text like 'Hook Factory v2.0 is a comprehensive hook generation system' - just show the commands and let the code speak
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with extensive repetition. Explains concepts Claude knows (what hooks are, basic file structures), repeats feature lists multiple times, and includes marketing-style language ('NEW!', 'Key Features') that wastes tokens. | 1 / 3 |
Actionability | Provides fully executable commands throughout - CLI invocations, installation commands, and concrete code examples. The hook.json example is copy-paste ready, and all three generation modes have clear, specific invocation syntax. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows with explicit validation checkpoints. The Installation Flow diagram shows backup → validate → merge → atomic write → validate → rollback pattern. Interactive mode has numbered 7-question flow with validation at each step. | 3 / 3 |
Progressive Disclosure | References external files (README.md, examples/, templates.json) appropriately, but the SKILL.md itself is monolithic with content that should be in separate files (full troubleshooting guide, complete architecture diagrams, version history). The examples directory structure is mentioned but inline content is excessive. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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.