autonomy--sre-agent

Diagnose production issues by querying logs, metrics, and traces from CLIs.

57|3|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/patterninc/code-mint --skill autonomy-sre-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomy--sre-agent
Source: https://github.com/patterninc/code-mint/tree/main/.agents/skills/autonomy--sre-agent
Command: npx skills add https://github.com/patterninc/code-mint --skill autonomy-sre-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnosing complex production issues by querying logs, metrics, and traces from observability, cloud, and CI/CD CLIs to quickly identify root causes and reduce mean time to resolution.

Core Features & Use Cases

  • Investigation workflow: check error rates, search logs, correlate traces, assess service health, and align deployments with incident timing.
  • Hypothesis-driven analysis: generate, rank, and test candidate root causes with structured evidence and safe remediation guidance.
  • Onboarding reference: includes a complete worked example using Datadog Pup, AWS CLI, and GitHub CLI, with project-customization guidance for infrastructure notes.

Quick Start

Start an investigation by following the prescribed workflow to collect signals and form actionable hypotheses.

Frequently Asked Questions about autonomy--sre-agent

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

FAQPage Schema
How do I diagnose production issues using logs, metrics, and traces?

To diagnose production issues, query logs, metrics, and traces from observability, cloud, and CI/CD CLIs to collect signals and form actionable root-cause hypotheses. The workflow checks error rates, correlates traces, and aligns deployments with incident timing.

What is the best way to investigate a service health check during an incident?

The best way to investigate a service health check is applying a structured investigation workflow that queries observability data to assess service health, gather evidence, and test candidate root causes with safe remediation guidance.

How do I reproduce reported bugs with evidence from CI/CD and cloud CLIs?

To reproduce reported bugs with evidence, align deployment timing from CI/CD pipelines with cloud CLI logs and metrics to verify the incident context. This hypothesis-driven analysis generates ranked root causes supported by structured evidence.

Can I use Datadog, AWS CLI, and GitHub CLI for root-cause analysis?

Yes, you can use Datadog, AWS CLI, and GitHub CLI for root-cause analysis. The investigation workflow queries these observability, cloud, and CI/CD CLIs to correlate signals, validate hypotheses, and plan safe remediation.

When do I need a hypothesis-driven analysis for incident investigations?

You need hypothesis-driven analysis for incident investigations when complex production issues require querying multiple observability sources. It generates, ranks, and tests candidate root causes using collected logs and metrics to reduce mean time to resolution.