slo-check-status

Monitors SLO health, budgets, and trends with machine-friendly outputs for gpxtoolkit.io users.

535|42|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/grafana/gcx --skill slo-check-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slo-check-status
Source: https://github.com/grafana/gcx/tree/main/claude-plugin/skills/slo-check-status
Command: npx skills add https://github.com/grafana/gcx --skill slo-check-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically surfaces SLO health, budget burn, and trends to inform quick decision-making and prioritization.

Core Features & Use Cases

  • Overview of SLO health, budget consumption, and trend data for all SLOs or a specific SLO.
  • Route to investigation or optimization when issues are detected.
  • Generate concise status summaries to guide incident response and SLO management.

Quick Start

Ask gcx to show the status of all SLO definitions.

Frequently Asked Questions about slo-check-status

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

FAQPage Schema
How do I check SLO health and error budget status?

The Skill monitors SLO health by returning health status, SLI, remaining error budget, burn rate, and timelines for all SLOs or a specific one, producing machine-friendly outputs for quick decision-making.

What is SLO burn rate and how does it relate to error budget consumption?

SLO burn rate measures how quickly your error budget is being consumed. Monitoring burn rate alongside remaining error budget helps you prioritize incident response and identify services needing optimization.

How do I monitor SLO budgets across all definitions at once?

You can monitor SLO budgets across all definitions by requesting a full status overview. This surfaces budget consumption and trend data for every SLO, enabling quick prioritization of at-risk services.

Does this SLO monitoring tool work with gcx command conventions?

Yes, this SLO monitoring tool adheres to gcx command conventions and produces machine-friendly outputs. It is designed to return status summaries suitable for agent processing and automated workflows.

When should I investigate SLO health trends for incident response?

You should investigate SLO health trends when error budget burn rate accelerates or health status degrades. The generated status summaries guide incident response by routing to investigation when issues are detected.