Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides the technical patterns needed to interface with Axiom via API. It enables the programmatic creation of dashboards, including chart configuration and layout management, while facilitating migrations from legacy systems like Splunk.
Developers can use these skills to run metrics queries against MetricsDB, discover available tags, and investigate OTel metrics data through structured scripts.
WHO IT'S FOR
AI agent / automation builders
evaluate OpenClaw agent performance on real-world tasks
LLM researchers
compare model capabilities and submit leaderboard results
Observability engineers
build Axiom dashboards and query metrics via API
Platform / DevEx teams
migrate logging and monitoring from Splunk to Axiom
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
An Axiom deployment configured in `~/.axiom.toml` with its URL, API token, and organization ID
Run this command in a terminal to install query-metrics for Amp.
amp skill add axiomhq/skills/query-metrics
Create `~/.axiom.toml`. Replace the documented deployment name, URL, `xaat-your-api-token`, and `your-org-id` placeholders with the corresponding Axiom deployment values; use a scoped API token with the permissions required by the workflow.
In a terminal, from the installed query-metrics skill folder, run its setup script to check `curl`, `jq`, and `~/.axiom.toml`.
Installs: The query-metrics skill selected from the axiomhq/skills collection · Claude Code, Cursor, Codex
Before you start
A target dataset of kind `otel:metrics:v1`
jq
curl
An Axiom deployment configured in `~/.axiom.toml` with its URL, API token, and organization ID
Run this command in a terminal to select and install query-metrics.
npx skills add axiomhq/skills -s query-metrics
Create `~/.axiom.toml`. Replace the documented deployment name, URL, `xaat-your-api-token`, and `your-org-id` placeholders with the corresponding Axiom deployment values; use a scoped API token with the permissions required by the workflow.
In a terminal, from the installed query-metrics skill folder, run its setup script to check `curl`, `jq`, and `~/.axiom.toml`.
Installs: Complete axiomhq/skills bundle, including the documented dependencies of building-dashboards
Before you start
jq
curl
A target dataset of kind `otel:metrics:v1` when using query-metrics
The axiom-sre and query-metrics skill dependencies, which the documented bundle command includes
An Axiom deployment configured in `~/.axiom.toml` with its URL, API token, and organization ID
Run this command in a terminal to install the complete axiomhq/skills bundle.
npx skills add axiomhq/skills
Create `~/.axiom.toml`. Replace the documented deployment name, URL, `xaat-your-api-token`, and `your-org-id` placeholders with the corresponding Axiom deployment values; use an advanced API token with minimal privileges.
In a terminal, from the installed building-dashboards skill folder, run its setup script to check `curl`, `jq`, and `~/.axiom.toml` and make the bundled scripts executable.
<skill_directory>: path to the cloned PinchBench skill directory
<provider/model>: provider-prefixed model identifier
Python 3.10+, uv, and a running OpenClaw instance
Use the pinchbench skill to run only `task_sanity` with `--no-upload` from <skill_directory>, using my provider-prefixed model ID <provider/model>. Report the locally saved result and do not register a token or upload anything.
<deployment>: deployment name configured in `~/.axiom.toml`
A configured Axiom URL, scoped API token, and organization ID
jq and curl
Use the query-metrics skill to list only metrics datasets for Axiom deployment <deployment>. Return each dataset's name, edge deployment, and kind; do not run a metrics query yet.
<audience>: for example, on-call responders, a service team, or executives
<decision>: the decision the dashboard should support
<service-or-scope>: service, environment, region, cluster, endpoint, or cross-service scope
Known dataset kind and schema details, if available
Use the building-dashboards skill to draft a dashboard blueprint for <audience> making <decision> about <service-or-scope>. Organize it from overview to drilldown to evidence, identify the question and action for each proposed panel, and ask for any missing dataset-kind or schema details. Do not deploy or create the dashboard.