hook-diagnostics
Diagnose Claude Code hook installation, delivery, and ingestion issues. Checks hook configuration, connectivity, event flow, and identifies common problems. Use when events are not appearing in the dashboard.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill hook-diagnostics --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Hook Diagnostics Diagnose hook integration issues between Claude Code and the Agent Monitor. ## Input The user provides: **$ARGUMENTS** This may be: - "full" or empty (default: run all diagnostics) - "install" to check hook installation only - "connectivity" to check dashboard connectivity only - "events" to check event delivery only ## Procedure Run diagnostic checks in this order: ### 1. Hook Installation Check Verify hooks are installed in Claude Code settings: ```bash # Check if hooks exist in Claude Code settings cat ~/.claude/settings.json | jq '.hooks // empty' ``` Verify: - All 7 expected hook types are registered: `PreToolUse`, `PostToolUse`, `Stop`, `SubagentStop`, `Notification`, `SessionStart`, `SessionEnd` - Hook commands point to the correct handler script path - Handler script exists and is readable at the configured path ### 2. Dashboard Connectivity Test that the dashboard API is reachable: ```bash curl -sf http://localhost:4820/api/health ``` Verify: - Dashboard responds with 200 OK - Response includes expected health fields - WebSocket endpoint is accessible ### 3. Hook Handler Validation Check the hook handler script: ```bash # Verify handler exists and is exe
- Input
- Procedure
- 1. Hook Installation Check
- 2. Dashboard Connectivity
- 3. Hook Handler Validation
- 4. Event Delivery Test
- 5. Database Check
- 6. Recent Event Flow
- Output Format
Check if hooks exist in Claude Code settings
cat ~/.claude/settings.json | jq '.hooks // empty'
curl -sf http://localhost:4820/api/health
Verify handler exists and is executable
ls -la <handler-path>
Syntax check
node --check <handler-path>
echo '{"hook_type":"test","session_id":"diag-test","data":{}}' | \
curl -sf -X POST http://localhost:4820/api/hooks/event \
curl -sf http://localhost:4820/api/statsWhat does the hook-diagnostics skill do?
Diagnose Claude Code hook installation, delivery, and ingestion issues. Checks hook configuration, connectivity, event flow, and identifies common problems. Use when events are not appearing in the dashboard.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill hook-diagnostics --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.