Skip to content
TrustedSkillsbeta
Back to all skills

Debug Hooks

Checked
parcadei·vlatest·testing·MIT

Insert temporary debugging code snippets into running programs to isolate issues and accelerate troubleshooting.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add parcadei/continuous-claude-v3 --skill debug-hooks -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

parcadei

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned parcadei/continuous-claude-v3 at d07ff4b06b.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d07ff4b06b
Manifest
.claude/skills/debug-hooks/SKILL.md
Scanned
1 file, 110 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Debug Hooks skill provides a systematic workflow for troubleshooting Claude Code hooks, enabling you to diagnose and resolve issues related to their behavior. It allows you to insert temporary debugging code snippets into running programs to isolate problems and accelerate troubleshooting when your hooks aren't behaving as expected. This is particularly helpful when investigating why hooks fire, produce incorrect output, or fail to trigger under specific circumstances.

When to use it

This skill is useful in the following situations:

  • When a hook isn’t firing at all.
  • When a hook produces unexpected or incorrect output.
  • When a SessionEnd event isn't working as intended.
  • When a PostToolUse hook fails to trigger.
  • To understand why a hook didn't run when you expected it to.

Key capabilities

  • Provides steps for checking hook outputs and cache locations.
  • Offers methods for verifying hook registration in project and global settings files.
  • Includes instructions for testing hooks manually using shell commands.
  • Highlights the issue of silent failures caused by detached spawn processes and provides a fix with temporary logging.
  • Details how to rebuild TypeScript-based hooks after making edits.

Example prompts

Here are some examples of what you might instruct an AI agent equipped with this skill to do:

  • "Check why my SessionEnd hook isn't running."
  • "Verify the registration of my PostToolUse hook in my project settings."
  • "Test my session-end-cleanup.sh hook manually."

Tips & gotches

  • Rebuild after edits: If you modify TypeScript source files, remember to rebuild the hooks using npx esbuild as changes to source code alone won't be reflected.
  • Silent failures: Be aware that detached spawn processes with redirected standard input/output can hide errors; add temporary logging to capture and diagnose these issues.
  • Duplicate registration: Hooks can sometimes run twice if registered in both project and global settings – ensure there are no duplicates.