feat(metrics): harden metrics scripts and correct discovery-time docs
Axiom Skills
Agent skills for working with Axiom. Skills are folders of instructions, scripts, and resources that coding agents load dynamically to improve performance on specialized tasks.
Available Skills
| Skill | Description |
|---|---|
| sre | Hypothesis-driven SRE investigation with Axiom |
| spl-to-apl | Translate Splunk SPL queries to Axiom APL |
| building-dashboards | Design and build Axiom dashboards from intent, templates, Splunk migrations, and metrics/MPL chart payloads (works with query-metrics) |
| axiom-alerting | Unified monitor + notifier management for Axiom alerting via the v2 API |
| controlling-costs | Analyze query patterns to find unused data and optimize Axiom costs |
| query-metrics | Run metrics queries against Axiom MetricsDB and discover available metrics, tags, and values |
| metrics-chart | Render metrics query results (application/vnd.metrics.v3+json) as line charts; zero-dependency ASCII by default, optional gnuplot PNG/SVG/sixel (pairs with query-metrics) |
| writing-evals | Scaffold evaluation suites for the Axiom AI SDK |
Requirements
- jq - JSON processor (
brew install jqorapt install jq) - curl - HTTP client (usually pre-installed)
- bc - Calculator, needed by controlling-costs (
brew install bcorapt install bc)
MCP Server
.mcp.json configures the hosted Axiom MCP Server at https://mcp.axiom.co/mcp for agent clients that install plugins from a manifest. See the MCP setup docs.
Installation
npx skills add axiomhq/skills
This installs all skills. Skills have dependencies on each other (e.g., controlling-costs depends on sre and building-dashboards), so installing all is recommended.
After installing, run the setup script to configure Axiom access:
~/.config/agents/skills/sre/scripts/setup
Configuration
Most skills require access to Axiom. Create ~/.axiom.toml with your deployment(s):
[deployments.prod]
url = "https://api.axiom.co"
token = "xaat-your-api-token"
org_id = "your-org-id"
[deployments.staging]
url = "https://api.axiom.co"
token = "xaat-your-staging-token"
org_id = "your-staging-org-id"
To get these values:
org_id- The organization ID. Get it from Settings → Organization.token- Use an advanced API token with minimal privileges.
The deployment name (e.g., prod, staging) is passed to scripts: scripts/axiom-query prod "..."
License
MIT License - see LICENSE