What is slo-optimize?

An advisory tool that analyzes Grafana service-level objective (SLO) trends over 28 days. An SLO is a target for how reliably a service should work, such as its availability.

Use it to review SLO performance, consider changes to objectives, alert sensitivity, labels, or time windows, and decide what should be changed elsewhere.

It replaces general tuning advice with recommendations based on the SLO’s observed timeline and measured values.

slo-optimize — 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-optimize

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-optimize/github.svg)](https://agentmods.dev/skills/grafana/gcx/slo-optimize)

Your own site

<a href="https://agentmods.dev/skills/grafana/gcx/slo-optimize"><img src="https://agentmods.dev/badge/skills/grafana/gcx/slo-optimize/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-optimize"><img src="https://agentmods.dev/badge/skills/grafana/gcx/slo-optimize.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,804 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.00065	$0.02804
Opus 5.5	$0.00026	$0.01122
Sonnet 5.5	$0.00013	$0.00561
Haiku 4.5	$0.00006	$0.00280

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

Security

Grade A, and why

slo-optimize 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-optimize/SKILL.md · 287 lines

How it starts

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

SLO Optimizer

Analyze SLO timeline trends, compute statistics over the past 28 days, and generate advisory recommendations backed by real metric values. Never modify SLO definitions directly — route to slo-manage when the user wants to apply a recommendation.

Core Principles

Use gcx commands exclusively — do not call Grafana APIs directly.
Trust the user's expertise — skip explanations of what SLOs or burn rates are.
Use -o json for agent processing of structured output; default format for user display.
Show graph output for timeline data so the user can see the trend visually.
Every recommendation MUST include supporting data (current values, projected values, or historical comparisons). No generic advice without numbers.
This skill is advisory only. Route to slo-manage for any changes the user wants to apply.

Prerequisites

gcx configured with a context pointing to the target Grafana instance.

If the user does not supply a UUID, list available SLOs first:

gcx slo definitions list

Ask the user which SLO to analyze if the target is ambiguous.

Optimization Workflow

Step 1: Retrieve SLO Definition

gcx slo definitions get <UUID> -o json

Extract and note:

spec.name — display name
spec.objectives[0].value — current objective (e.g., 0.999)
spec.objectives[0].window — compliance window (e.g., 28d)
spec.query.type — ratio | freeform | threshold
spec.query.ratio.groupByLabels — dimensional labels (may be empty)
spec.alerting — fastBurn / slowBurn configuration (may be absent)
spec.destinationDatasource.uid — datasource UID for metric queries

Step 2: Fetch 28-Day Timeline

# Default graph output for user display
gcx slo definitions timeline <UUID> --from now-28d --to now

# JSON output for statistical analysis
gcx slo definitions timeline <UUID> --from now-28d --to now -o json

Parse the JSON output to extract SLI values across the time series. Compute:

mean_sli — average SLI over the 28-day window
min_sli — lowest observed SLI point
max_sli — highest observed SLI point
std_dev — variability indicator

Read the full file on GitHub · 287 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 · -62 tokens per session f74a021d400e
2mo ago First seen · 291 lines · 127 tokens per session scan A 4593e61a2ee2

Subscribe to this mod's changes

slo-optimize is a skill published in the GitHub repository grafana/gcx (817 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 2,804 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

slo-optimize next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
slo-optimizegrafana/gcx	Skill	817	today	Apache-2.0	A	65	Claude Code
imagegenopenai/codex	Skill	133k	today	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
chat-pet-sprite-creationmicrosoft/vscode	Skill	195k	today	MIT	A	53	Claude Code, Codex