hook-developer

Develop Maestro hooks with input/output schemas and registration methods.

8|1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/scooter-lacroix/Maestro --skill hook-developer-scooter-lacroix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hook-developer
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/hook-developer
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill hook-developer-scooter-lacroix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive reference for developing Maestro hooks, ensuring correct input/output schemas, registration, and testing patterns, thereby streamlining the creation and debugging of custom hook logic.

Core Features & Use Cases

  • Schema Reference: Detailed input/output schemas for all Maestro hook events (e.g., PreToolUse, PostToolUse, UserPromptSubmit).
  • Registration Guidance: Clear examples on how to register hooks in settings.json, including matcher patterns.
  • Hook Types: Explanations and examples for both command and prompt-based hooks.
  • Use Case: When developing a new custom hook to validate user input before it's processed by an agent, consult this Skill to understand the exact JSON structure required for the UserPromptSubmit hook's input and expected output.

Quick Start

Refer to the PreToolUse hook input schema to understand available fields for modifying tool calls.

Frequently Asked Questions about hook-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I develop Maestro hooks for PreToolUse and PostToolUse events?

To develop Maestro hooks, you need the correct input and output JSON schemas for events like PreToolUse and PostToolUse. This Skill provides comprehensive schema references and testing patterns to ensure your custom logic correctly intercepts and modifies tool calls.

How do I register command and prompt-based hooks in settings.json?

Registering Maestro hooks in settings.json involves defining the hook type, specifying matcher patterns, and configuring either command or prompt-based execution. This Skill offers clear examples for correctly structuring your settings.json file to activate custom hooks.

What environment variables and exit codes are available for Maestro hook debugging?

Maestro hook debugging relies on specific environment variables and exit codes to control execution flow and signal errors. This Skill details the available environment variables and exit code conventions to facilitate robust hook creation and debugging.

Can I use a UserPromptSubmit hook to validate user input before agent processing?

Yes, the UserPromptSubmit hook validates user input before an agent processes it by defining the exact JSON structure required for the hook's input and expected output. This Skill explains how to implement this validation pattern.

What are the limitations when creating custom Maestro hooks for tool call modification?

Limitations when creating custom Maestro hooks include strict adherence to expected input/output schemas and correct exit code handling to avoid breaking the agent workflow. This Skill outlines testing patterns to verify your hooks handle edge cases properly.