What is slo-check-status?

A tool workflow for checking service-level objective health in Grafana. An SLO is a target for how reliably a service should work, measured using indicators such as errors or availability.

Use it to review all SLOs or one specific SLO, including health, error budget, burn rate, and recent performance trends.

It shows whether services are meeting their reliability targets and how quickly their allowed error budget is being used.

slo-check-status — Skill for Claude Code by grafana/gcx

About the project

gcx is a command-line tool that lets people and AI coding agents manage and inspect Grafana Cloud, Enterprise, and open-source instances. It provides access to dashboards, alerts, SLOs, metrics, logs, and traces, with workflows for alert investigation, dashboard management, GitOps, and observability setup. Its catalogue entries provide agent instructions and extensions for using gcx.

grafana/gcx · 817 stars · on GitHub · grafana.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add grafana/gcx --skill slo-check-status

Clone the repo

git clone --depth 1 https://github.com/grafana/gcx

Made for: Claude Code.

Or install gcx, the plugin that ships this one along with the rest of its 24 skills, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/grafana/gcx/slo-check-status/github.svg)](https://agentmods.dev/skills/grafana/gcx/slo-check-status)

Your own site

<a href="https://agentmods.dev/skills/grafana/gcx/slo-check-status"><img src="https://agentmods.dev/badge/skills/grafana/gcx/slo-check-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/grafana/gcx/slo-check-status"><img src="https://agentmods.dev/badge/skills/grafana/gcx/slo-check-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,383 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00072	$0.01383
Opus 5.5	$0.00029	$0.00553
Sonnet 5.5	$0.00014	$0.00277
Haiku 4.5	$0.00007	$0.00138

Measured 14d ago against content hash ed6e98f8bf85, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

slo-check-status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude-plugin/skills/slo-check-status/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SLO Status Checker

Check SLO health, budget consumption, and trends. Route to investigation or optimization as needed.

Core Principles

Use gcx commands — do not call Grafana APIs directly
Trust the user's expertise — no hand-holding or excessive explanation
Use -o json for agent processing, default format for user display
Show graphs for time-series data (timeline commands default to graph output)

Workflow

Step 1: Overview or Specific SLO

If the user asks about all SLOs (no specific UUID):

gcx slo definitions list

This shows UUID, name, target objective, window, and status for all SLOs.

Then get the health summary:

gcx slo definitions status

This shows SLI, error budget, and health status for all SLOs in a table.

If the user asks about a specific SLO (UUID or name provided):

gcx slo definitions status <UUID> -o wide

The -o wide output includes additional columns: BURN_RATE, SLI_1H, and SLI_1D, which give a richer picture of recent performance.

Step 2: Interpret Status Values

Status	Meaning
OK	SLI >= objective. SLO is healthy.
BREACHING	SLI < objective. Error budget is being consumed.
NODATA	No Prometheus metrics from recording rules.
Creating	SLO provisioning in progress.
Updating	SLO update in progress.
Deleting	SLO deletion in progress.
Error	SLO in error state — check the SLO configuration.

NODATA handling: Recording rule metrics may not be available if the destination datasource is misconfigured or recording rules are not evaluating. Note this to the user and suggest checking the destination datasource configuration.

Step 3: Timeline (Conditional)

Show the timeline when:

The user asks about trends or historical data
Any SLO shows BREACHING status

All SLOs timeline:

gcx slo definitions timeline --from now-7d --to now

Specific SLO timeline:

gcx slo definitions timeline <UUID> --from now-7d --to now

Read the full file on GitHub · 160 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

14d ago Changed · +4 lines · -59 tokens per session ed6e98f8bf85
2mo ago First seen · 156 lines · 131 tokens per session scan A e775c8115d08

Subscribe to this mod's changes

slo-check-status is a skill published in the GitHub repository grafana/gcx (817 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 1,383 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Analytics and metrics Cloud DevOps and cloud

slo-check-status next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
slo-check-statusgrafana/gcx	Skill	817	today	Apache-2.0	A	72	Claude Code
gke-compute-classesgoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
gke-workload-securitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	171	Claude Code, Codex
gke-reliabilitygoogle/skills	Skill	22k	yesterday	Apache-2.0	A	85	Claude Code, Codex
cloud-architectJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	71	Claude Code
nemo-automodel-launcher-configNVIDIA/skills	Skill	3.9k	yesterday	Apache-2.0	A	30	Claude Code
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	78	Claude Code