debug-live-issue
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting
$ npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill webhook-management --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/webhook-managementContext preview
The summary Claude sees to decide when to auto-load this skill.
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting
name: webhook-management description: > Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
1. Run `ccam webhooks providers` and select the exact provider key. 2. Run `ccam webhooks` to inspect existing redacted targets. 3. Build the JSON body in a local file. Keep tokens, routing keys, and webhook URLs out of chat and logs. 4. Show the target name, provider, rule scope, and whether a real test message will be sent. 5. Create or update only after confirmation:
ccam webhooks create --file /secure/path/target.json --yes ccam webhooks update <id> --file /secure/path/patch.json --yes
6. Ask again before `ccam webhooks test <id>`. It sends an external message. 7. Inspect results with `ccam webhooks deliveries <id>`.
Never print secret fields. The dashboard returns masked values by design.
🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, & an interactive web UI/MacOS/Windows native app.
Repo: hoangsonww/Claude-Code-Agent-Monitor
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data…
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start…
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored…
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or…
Push the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is…
Onboard quickly to this repository. Use when asked to understand architecture, locate ownership, choose the right module, or identify the correct commands and…