hook-factory

I was curious about how you're structuring the hook lifecycle—managing the event emission, dependency resolution, and cleanup in a single factory pattern feels like it could get complex fast. How are you handling cases where hooks need to fire in a specific order or have interdependencies?

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 69/100, solidly in D territory. This is based on Anthropic's skill quality rubric—think of it as how well your skill balances token efficiency, clarity, and practical value. Your strongest area is Ease of Use (19/25)—the metadata and workflow structure are solid. The biggest drag is Progressive Disclosure Architecture (20/30)—you've got a 462-line SKILL.md that's trying to do too much in one place.

What's Working Well

• Clear modes and templates: Three distinct usage patterns (auto-format, test-runner, git-auto-add) with 10 templates give users concrete options to work with
• Solid metadata structure: Your frontmatter is valid, name conventions are correct, and the skill is technically discoverable
• Practical examples: You've included actual Q&A interactions showing how the skill works in practice, which helps users understand the flow

The Big One: Missing Reference Architecture

Here's what's holding you back the most: Your SKILL.md claims an examples/ directory with 10 reference folders (auto-format-python/, git-auto-add/, test-runner/, etc.), but these files don't actually exist. This breaks Progressive Disclosure—you're promising layered reference material that isn't there, and it costs you 8 points.

Why it matters: A 462-line monolithic file is hard to navigate and token-expensive. Progressive Disclosure means building a pyramid: thin skill definition at the top, detailed references only when needed.

The fix: Either create actual reference files in an examples/ directory with detailed specs for each template, or remove the mentions entirely and restructure SKILL.md to be self-contained (max ~300 lines). If you go the reference route, structure it like:

hook-factory/
├── SKILL.md (definition + brief overview)
├── MODES.md (detailed explanation of the three modes)
├── TEMPLATES.md (reference for all 10 templates)
└── TROUBLESHOOTING.md (diagnostics and edge cases)

Impact: +8 points if you build the references properly.

Other Things Worth Fixing

1. Add trigger phrases to your description (Medium priority, +2 points)

   • Current: "Generate production-ready Claude Code hooks..."
   • Add explicit activation keywords: "Use when: auto-format code, run tests on completion, stage files with git, load context at session start"

2. Strip the marketing language (Medium priority, +3 points)

   • Remove superlatives like "production-ready," "comprehensive," "NEW!" and emojis (✅❌)
   • Plain language is stronger: "Detects missing tools and uses silent failure mode" instead of "Comprehensive safety features: ✅ Tool detection"

3. Fix the second-person perspective (Medium priority, +2 points)

   • Replace dialogue format ("You:", "Hook Factory:") with imperative instructions
   • Change "You want to auto-format Python" → "Generate hook for auto-formatting Python files"

Quick Wins

• Create the missing reference files (biggest impact)
• Add specific trigger keywords to metadata description
• Remove marketing fluff and emoji decoration
• Restructure examples as dialogue-free, imperative instructions
• Most impactful first: fix the PDA architecture, then address trigger clarity

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.