slo-manage

Manage Grafana SLO definitions with gcx YAML templates and dry-run validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating and maintaining Grafana SLO definitions is error‑prone when done manually; this skill centralizes the lifecycle via gcx, enabling consistent creation, updates, pulls, pushes, and deletions with guardrails.

Core Features & Use Cases

  • Create, update, pull, push, and delete SLO definitions using gcx YAML templates.
  • GitOps sync workflows: pull all SLOs to disk and push changes back to Grafana with dry-run validation.
  • Safe operations: dry-run checks, proper destination datasource resolution, and standardized templating via references/templates.

Quick Start

Define an SLO YAML, then push it with gcx slo definitions push slo.yaml --dry-run to validate the changes.

Frequently Asked Questions about slo-manage

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

FAQPage Schema
How do I manage Grafana SLO definitions using a GitOps workflow?

You can manage Grafana SLO definitions through GitOps by using gcx to pull existing SLOs to disk as YAML templates, push changes back to Grafana, and synchronize across multiple instances with dry-run validation.

What is the safest way to update Grafana SLOs without causing configuration errors?

The safest way to update Grafana SLOs is to use gcx dry-run validation, which applies guardrails like proper destination datasource resolution and standardized templating to prevent unsafe operations before pushing changes.

Can I use YAML templates to create and delete Grafana SLOs?

Yes, you can create, update, and delete Grafana SLO definitions using gcx YAML-based templates, which centralize the lifecycle management and ensure consistent configuration across your monitoring instances.

How do I sync SLO configurations across different Grafana instances?

You can sync SLO configurations across Grafana instances by pulling SLO definitions to local YAML files and pushing them to target destinations using gcx, leveraging dry-run checks and datasource resolution for safe synchronization.

Why do I need dry-run validation when pushing SLO definitions to Grafana?

Dry-run validation is needed when pushing SLO definitions to Grafana because it applies guardrails that verify destination datasource resolution and template standardization, preventing unsafe operations and manual configuration errors.

Does gcx support pulling existing Grafana SLOs to local storage?

Yes, gcx supports pulling all existing Grafana SLO definitions to local disk as YAML files, enabling GitOps synchronization, offline updates, and consistent lifecycle management across your monitoring environments.