webhook-management — Claude Code skill for webhook setup
Configure CCAM webhook targets, connect them to alert rules, and inspect delivery records. Use the skill when managing notification endpoints from the CLI.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill webhook-management -a claude-codeWhat webhook-management does
The skill guides you through checking provider keys with ccam webhooks providers, reviewing existing targets, and preparing a JSON file to create or update one. It also covers alert-rule scope, test notifications, delivery history, and target removal.
Before a target is created or changed, the agent presents its name, provider, and rule scope for confirmation. A test needs its own confirmation because it sends a message outside the project. Keep tokens, routing keys, and webhook URLs out of chat and logs; the dashboard masks secret values.
The skill can be installed in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, or OpenCode. Target settings go in a local JSON file, passed to the CLI with --file.
What it helps with
- find the exact key for a webhook provider
- create or update a target from a JSON file
- restrict a target to selected alert rules
- send a test notification after confirmation
- inspect delivery history or remove a target
Example prompts for the agent
- List CCAM webhook providers and help me configure a target for the provider I choose.
- Create a webhook target from
target.jsonand scope it to the relevant alert rules. - Review deliveries for this target ID and prepare a test notification for my approval.
How to install webhook-management
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill webhook-management -a claude-code2Manually: put the files in place
~/.claude/skills/webhook-management/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/webhook-management/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill webhook-management -a codex2Manually: put the files in place
.agents/skills/webhook-management/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill webhook-management -a cursor2Manually: put the files in place
.cursor/skills/webhook-management/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hoangsonww/Claude-Code-Agent-Monitor webhook-management2Manually: put the files in place
.github/skills/webhook-management/SKILL.md1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill webhook-management -a gemini-cli2Platform CLI
gemini skills install https://github.com/hoangsonww/Claude-Code-Agent-Monitor --path plugins/ccam-integrations/skills/webhook-managementManually: put the files in place
.devin/skills/webhook-management/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill webhook-management -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about webhook-management
How do I install webhook-management in Claude Code?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill webhook-management -a claude-code. The skill file is at ~/.claude/skills/webhook-management/SKILL.md.
What does webhook-management do?
It guides CCAM webhook setup, including provider selection, target changes, alert-rule scope, test messages, and delivery-history checks.
Does a webhook test send a real message?
Yes. ccam webhooks test <id> sends a message externally, so the agent must ask for separate confirmation before running it.
Source text
SKILL.md · MIT
--- 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. --- # Webhook Management 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: ```bash 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.
© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor
