Do I need TypeScript to build Maestro hooks?

No, while TypeScript is recommended for complex logic, you can use any language capable of reading from stdin and writing to stdout, including simple Shell scripts.

What are Maestro hooks?

Maestro hooks are specialized scripts or prompts that trigger during Claude Code lifecycle events, allowing developers to modify behavior, block actions, or inject context.

Can hooks block tool execution?

Yes, hooks like PreToolUse and UserPromptSubmit can block actions by returning specific JSON outputs or using exit code 2.

What is the difference between a command hook and a prompt hook?

Command hooks execute local scripts or binary commands, while prompt hooks utilize a secondary LLM (Haiku) to make context-aware decisions based on a prompt template.

How do I test my Maestro hooks manually?

You can test hooks by piping a JSON representation of the hook's input schema directly into your hook script via the command line.

Maestro Hook Developer

Name: Maestro Hook Developer
Author: scooter-lacroix

byscooter-lacroix

Developer Tools

Provides a comprehensive reference and implementation guide for building custom Maestro lifecycle hooks for Claude Code.

About

Maestro Hook Developer is an essential resource for developers looking to extend Claude's capabilities through the Maestro framework. It provides detailed schemas for every hook event—from tool execution and session management to user prompts and subagent control—enabling the creation of sophisticated workflows that can block tool calls, inject context, or automate permissions. Whether you are building custom bash-based hooks or LLM-driven prompt hooks, this skill ensures correct integration, robust testing patterns, and efficient session management through a standardized development approach.

Key Features

Standardized TypeScript and Shell wrapper implementation patterns for rapid development
Manual testing commands and debugging protocols for validating hook behavior
0 GitHub stars
Step-by-step registration guide for settings.json using advanced matcher patterns
Detailed input/output schemas for all Maestro hook events including PreToolUse and SessionStart
Comprehensive reference for environment variables, MCP tool naming, and exit codes

Use Cases

Injecting project-specific context into every user prompt automatically
Automating permission approvals for specific tools via PermissionRequest hooks
Implementing custom validation logic to block or modify dangerous tool executions

About

Key Features

Standardized TypeScript and Shell wrapper implementation patterns for rapid development
Manual testing commands and debugging protocols for validating hook behavior
0 GitHub stars
Step-by-step registration guide for settings.json using advanced matcher patterns
Detailed input/output schemas for all Maestro hook events including PreToolUse and SessionStart
Comprehensive reference for environment variables, MCP tool naming, and exit codes

Use Cases

Injecting project-specific context into every user prompt automatically
Automating permission approvals for specific tools via PermissionRequest hooks
Implementing custom validation logic to block or modify dangerous tool executions