Agent skill · marketing growth · axiomhq
axiom-alerting
Create and manage Axiom monitors and notifiers via the v2 public API. Use when building alerting, routing notifications, validating monitor behavior, and maintaining alert configurations end-to-end.
Why this skill is useful
Adds executable scripts for managing Axiom monitors and notifiers that are not publicly documented.
What it needs
Requires axiom installed locally. Requires axiom account access. About 4k tokens when loaded. Last updated 2026-07-14. 14 stars on the source repository.
What this skill does
Axiom Alerting You manage alerting in Axiom end-to-end: notifiers for routing and monitors for detection. API Overview Base URL: https://api.axiom.co/v2/ with Bearer token auth from .axiom.toml (project root or ~/.axiom.toml). Monitors (/v2/monitors) Operation Method Path ----------- -------- ------ List GET /v2/monitors Get GET /v2/monitors/{id} History GET /v2/monitors/{id}/history Create POST /v2/monitors Update PUT /v2/monitors/{id} Delete DELETE /v2/monitors/{id} Notifiers (/v2/notifiers) Operation Method Path ----------- -------- ------ List GET /v2/notifiers Get GET /v2/notifiers/{id} Create POST /v2/notifiers Update PUT /v2/notifiers/{id} Delete DELETE /v2/notifiers/{id} Prerequisites 1. Run scripts/setup 2. Ensure .axiom.toml has a deployment: Scripts Core: scripts/axiom-api <deploy> <method> <path> [body] Monitor scripts: scripts/monitor-list <deployment> [--json] scripts/monitor-get <deployment> <id> scripts/monitor-history <deployment> <id> <startTime> <endTime> scripts/monitor-create <deployment> <json-file> scripts/monitor-update <deployment> <id> <json-file> scripts/monitor-delete <deployment> <id> Notifier scripts: scripts/notifier-list <deployment> [--json] scripts/notifier-get <deployment> <id> scripts/notifier-create <deployment> <json-file> scripts/notifier-update <deployment> <id> <json-file> scripts/notifier-delete <deployment> <id> Recommended Workflow 1. Create notifier first. 2. Create monitor and set notifierIds. 3. Validate monitor behavior with monitor-history. 4. Iterate monitor thresholds and schedule. Workflow: End-To-End Alerting 1. Run scripts/setup. 2. List existing notifiers with scripts/notifier-list <deployment> and reuse one if appropriate. 3. If no suitable notifier exists, create one with scripts/notifier-create. 4. Create or update the monitor with notifierIds attached. 5. Validate with scripts/monitor-history <deployment> <id> <startTime> <endTime>. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills axiomhq/axiom-alerting