axiom-sre

Enforce hypothesis-driven incident investigations with Axiom queries and memory logging.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/NathanColosimo/kompose --skill axiom-sre-nathancolosimo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-sre
Source: https://github.com/NathanColosimo/kompose/tree/main/.agents/skills/axiom-sre
Command: npx skills add https://github.com/NathanColosimo/kompose --skill axiom-sre-nathancolosimo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill provides a hypothesis-driven, data-backed approach to incident response, enabling engineers to stabilize systems, perform rapid root-cause analysis, and learn from incidents via a persistent memory KB.

Core Features & Use Cases

  • Hypothesis-Driven Investigation: State, test, and disprove hypotheses using data queries and evidence.
  • Systematic Triage: Golden signals, USE/RED methodology, and memory integrations to prioritize fixes.
  • Memory System: A persistent knowledge base for patterns, queries, incidents, and runbooks that accelerates postmortems.
  • Axiom Integration: Query logs, execute APL queries, and generate shareable links to artifacts for collaboration.

Quick Start

Activate the skill with scripts/init and then begin incident investigations using discovery scripts and Axiom queries.

Frequently Asked Questions about axiom-sre

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

FAQPage Schema
What is hypothesis-driven incident response and how does it help root-cause analysis?

Hypothesis-driven incident response requires engineers to state, test, and disprove hypotheses using data queries and evidence. This systematic triage approach enforces data-backed investigations for root-cause analysis, stabilizing systems while logging findings to memory for future learning.

How do I run Axiom APL queries for live debugging during an incident?

You can execute Axiom APL queries for live debugging by first running initialization scripts, then using scripted discovery workflows to query logs. This generates shareable links to artifacts, enabling rapid collaboration and evidence gathering during incident triage.

Do I need jq and git to run Axiom triage and incident discovery workflows?

Yes, you need jq, git, and curl installed. These dependencies support the scripted discovery workflows, evidence recording, and memory KB integration required to enforce initialization and execute data-driven incident investigations properly.

What is the best way to prepare a postmortem after resolving an incident?

The best way to prepare a postmortem is using a persistent memory knowledge base that logs findings, patterns, queries, and runbooks during the incident. This accelerates postmortem preparation by capturing evidence and disproved hypotheses throughout the investigation.

Can I use USE and RED methodologies for systematic triage with Axiom logs?

Yes, you can apply USE and RED methodologies for systematic triage alongside Axiom log integration. The workflow prioritizes fixes by evaluating golden signals and executing APL queries to gather evidence, ensuring hypotheses are tested against actual system metrics.

Why does incident investigation require initialization before querying logs?

Initialization is required before querying logs to enforce discovery steps and ensure access to configured deployments and memory. This structured approach prevents unstructured troubleshooting, requiring data-driven, hypothesis-driven investigations that record evidence for future learning.