What causes a hook to run but produce no output?

This is frequently caused by using detached spawn processes with stdio set to ignore. This skill provides patterns to add temporary logging for debugging.

How can I test a hook manually without running a full session?

You can manually trigger a hook by piping a mock JSON payload into the specific shell script located in your .maestro/hooks directory.

Do I need to rebuild hooks after editing the source code?

Yes, if your hooks are written in TypeScript, you must rebuild the bundled .mjs file using esbuild for the changes to take effect in the shell wrapper.

Why isn't my Maestro hook firing?

Hooks often fail to fire due to missing registration in settings.json or incorrect file paths. Use this skill to verify both project and global settings.

Debug Hooks for Maestro

Name: Debug Hooks for Maestro
Author: scooter-lacroix

byscooter-lacroix

0•

Analytics & Monitoring

Troubleshoots and resolves issues with Maestro hooks by verifying registration, inspecting logs, and testing manual execution.

This skill provides a comprehensive diagnostic framework for Maestro hooks, addressing common issues like hooks not firing or producing incorrect outputs. It guides users through a systematic process that includes inspecting project caches, verifying registration in settings.json, testing shell wrappers manually, and diagnosing silent failures in detached processes. Whether you are dealing with SessionEnd triggers or PostToolUse logic, this skill ensures your automation hooks are correctly configured, compiled, and executing as expected within the Maestro environment.

Key Features

01Systematic verification of hook registration in global and project settings

02Step-by-step rebuild instructions for compiled TypeScript hook bundles

03Manual testing procedures for SessionEnd and PostToolUse events

040 GitHub stars

05Automated inspection of Maestro cache and debug logs

06Detection of silent failures in detached TypeScript/Node.js processes

Use Cases

01Validating hook execution paths and file permissions in new environments

02Investigating why a specific hook failed to trigger after a session or tool use

03Debugging incorrect output or state changes from a hook's shell wrapper

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add scooter-lacroix/maestro debug-hooks

For use in Claude.ai and ChatGPT

Key Features

01Systematic verification of hook registration in global and project settings

02Step-by-step rebuild instructions for compiled TypeScript hook bundles

03Manual testing procedures for SessionEnd and PostToolUse events

040 GitHub stars

05Automated inspection of Maestro cache and debug logs

06Detection of silent failures in detached TypeScript/Node.js processes

Use Cases

01Validating hook execution paths and file permissions in new environments

02Investigating why a specific hook failed to trigger after a session or tool use

03Debugging incorrect output or state changes from a hook's shell wrapper

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add scooter-lacroix/maestro debug-hooks

For use in Claude.ai and ChatGPT