hooks-builder
Create event-driven hooks for Claude Code automation. Use when the user wants to create hooks, automate tool validation, add pre/post processing, enforce security policies, or configure settings.json hooks. Triggers: create hook, build hook, PreToolUse, PostToolUse, event automation, tool validation, security hook
Security Assessment
Detected risks:
About hooks-builder
The hooks-builder skill allows users to create event-driven hooks for Claude Code automation, enabling seamless automation of tasks across different tool interactions and session states. By leveraging event-based triggers, this skill addresses the need for users to automate and customize workflows, enforce security policies, handle input/output processing, and maintain control over specific events during Claude’s execution. Whether it's creating hooks for pre/post processing, validating tool usage, or monitoring session states, this skill offers flexibility in automating various aspects of Claude’s behavior.
FAQ
How do I use hooks-builder for event-driven automation?
You can configure hooks for various events like PreToolUse, PostToolUse, SessionStart, etc. Each event can trigger actions such as blocking tool execution, modifying inputs, logging activity, or enforcing security policies.
Can hooks-builder be used across multiple projects?
Yes, hooks-builder supports hooks at the project level (committed team hooks), personal level (individual user hooks), and local overrides, allowing for flexibility across different environments.
What are the main limitations of hooks-builder?
Hooks are event-driven and may not block all actions, particularly in events like PostToolUse or Notification. Additionally, some events do not support matchers, and hooks cannot modify certain inputs after tool execution.
Install hooks-builder
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
mike-coulbourn/claude-vibes