axiom-sre

Formulate and test data-driven hypotheses against Axiom datasets.

14|1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/axiomhq/skills --skill axiom-sre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-sre
Source: https://github.com/axiomhq/skills/tree/main/skills/sre
Command: npx skills add https://github.com/axiomhq/skills --skill axiom-sre

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, git, python3, cloudflared, coreutils, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill anchors incident investigations to data, enabling hypothesis-driven debugging by querying Axiom observability resources and correlating logs, metrics, and traces. It reduces guesswork during outages and accelerates root cause identification.

Core Features & Use Cases

  • Hypothesis-Driven Investigation: State, test, and falsify hypotheses using targeted APL queries.
  • Memory-Backed Reasoning: Persist patterns, facts, and insights in a shared knowledge base for faster RCA.
  • Use Case: During production outages, run a sequence of queries to verify correlations between error spikes, latency, and service health.

Quick Start

To begin, activate the skill in a live incident and run: scripts/init to discover available environments, then scripts/setup to configure memory and Axiom access, and finally run scripts/axiom-query to fetch logs for your investigation.

Frequently Asked Questions about axiom-sre

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run hypothesis-driven incident investigations using Axiom observability data?

Hypothesis-driven incident investigation requires stating, testing, and falsifying hypotheses against Axiom datasets using targeted APL queries. You correlate logs, metrics, and traces to verify relationships between error spikes, latency, and service health during production outages.

What is the best way to triage production outages using logs, metrics, and traces?

Triage production outages by applying golden signals and RED/USE methodologies to correlate logs, metrics, and traces. This disciplined workflow anchors root cause analysis to data-driven observations rather than guesswork, accelerating service recovery.

How do I query Axiom datasets to correlate error spikes and latency during root cause analysis?

Query Axiom datasets by formulating targeted APL queries that test specific hypotheses about error spikes and latency. Fetch logs using the axiom-query script after configuring memory and Axiom access to verify correlations between service health metrics.

Do I need curl and jq installed to investigate incidents with Axiom logs?

Yes, you need curl and jq installed along with git, python3, cloudflared, and coreutils. These dependencies support the scripts that configure Axiom access, fetch observability data, and process query results during incident response.

Can I persist incident investigation patterns and facts for future root cause analysis?

Yes, the memory system persists investigation patterns, facts, and insights in a shared knowledge base. This memory-backed reasoning captures correlations and outcomes during incidents, enabling faster root cause identification in future investigations.

How does memory-backed reasoning improve SRE incident response workflows?

Memory-backed reasoning improves SRE workflows by storing patterns and facts from previous investigations in a shared knowledge base. This reduces guesswork during outages by providing historical context that accelerates root cause identification and correlation analysis.