---
name: hoangsonww-alert-management
description: "Inspect fired CCAM alerts and manage alert rules for token thresholds, event patterns, inactivity, and status duration. Use when acknowledging alerts, creating or editing a rule, checking cooldowns, or connecting alert rules to webhook targets."
license: "MIT"
metadata:
  decimalai-skill-id: "a39ace02-385b-4751-ab81-4fe46cc31f7f"
  decimalai-version-id: "569f7292-57aa-4d06-805c-62bf0bbbab95"
  decimalai-version: "1"
  decimalai-body-sha256: "2c9709fb2b75158dc0c3b9654cdb1457a6dc18049f70800b4f8a4af45a436399"
  decimalai-name: "hoangsonww/alert-management"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "agent-tooling"
  decimalai-source: "https://app.decimal.ai/s/hoangsonww-alert-management@1/SKILL.md"
---
# Alert Management

## Read

- `ccam alerts --unacked`
- `ccam alert-rules list`

## Write

Before changing anything, show the rule name, type, normalized config, enabled
state, and cooldown. Use `--yes` only after confirmation.

```bash
ccam alert-rules create --name "Token guard" --type token_threshold \
  --config '{"total_tokens":1000000}' --cooldown 300 --yes
```

Use `ccam alert-rules update <id> ... --yes` for partial edits and
`ccam alert-rules delete <id> --yes` for deletion. Acknowledgment changes the
feed state only. It does not change the rule or underlying session.

Never invent rule configs. Read the current rule and provider catalog first.