slo-optimize

slo-optimize is a skill for Claude Code from grafana/gcx. It costs 127 tokens per session (2,867 once invoked), scanned A, original, Apache-2.0.

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.

In plain words
What is it for?
Use it to review SLO performance, consider changes to objectives, alert sensitivity, labels, or time windows, and decide what should be changed elsewhere.
Why use it?
It replaces general tuning advice with recommendations based on the SLO’s observed timeline and measured values.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the gcx plugin — 24 skills, 1 agent shipped together

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 · 586 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.

agentmods
npx agentmods add skills/grafana/gcx/slo-optimize
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.

agentmods badge for slo-optimize

README.md
[![agentmods](https://agentmods.dev/badge/skills/grafana/gcx/slo-optimize.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.svg" alt="Measured on agentmods" height="20"></a>
Per session 127 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,867 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00127 $0.02867
Opus 5 $0.00063 $0.01434
Sonnet 5 $0.00025 $0.00573
Haiku 4.5 $0.00013 $0.00287

Measured 6d ago against content hash 4593e61a2ee2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 6d 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 · 291 lines

How it starts

The opening of the file, as written. The whole thing — 291 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

  1. Use gcx commands exclusively — do not call Grafana APIs directly.
  2. Trust the user's expertise — skip explanations of what SLOs or burn rates are.
  3. Use -o json for agent processing of structured output; default format for user display.
  4. Show graph output for timeline data so the user can see the trend visually.
  5. Every recommendation MUST include supporting data (current values, projected values, or historical comparisons). No generic advice without numbers.
  6. 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 · 291 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.

  1. 6d 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 (586 stars, last pushed yesterday), licensed Apache-2.0. It adds 127 tokens to every session and 2,867 once invoked, about $0.0006 per session on Opus 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens