What problem does it solve? Building Claude Code plugin hooks requires understanding multiple hook events, JSON output schemas, security constraints, and configuration formats, and mistakes can silently break user workflows or introduce injection vulnerabilities. ## Core Features & Use Cases - Hook Implementation Guidance: Covers all nine hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification) with both prompt-based and command hook patterns. - Validation and Testing Utilities: Ships scripts to validate hooks.json schema, test hook scripts with sample input, and lint hook code for security issues like unquoted variables and hardcoded paths. - Use Case: When adding a PreToolUse hook to block dangerous bash commands in a plugin, use this Skill to write the hooks.json entry with ${CLAUDE_PLUGIN_ROOT} paths, validate it with validate-hook-schema.sh, and test it with test-hook.sh before restarting Claude Code. ## Quick Start Create a PreToolUse prompt-based hook that validates file writes for path traversal and sensitive files, then validate the hooks.json configuration.
