add-provider

Automate adding Grafana Cloud product providers to gcx through gated stages.

535|42|Updated Mar 23, 2026

Search Tags:#design #research #onboarding #governance #grafana #provider #gcx

Ready to run

npx skills add https://github.com/grafana/gcx --skill add-provider-grafana

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-provider
Source: https://github.com/grafana/gcx/tree/main/.claude/skills/add-provider
Command: npx skills add https://github.com/grafana/gcx --skill add-provider-grafana

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates adding a new Grafana Cloud product provider to gcx — from API discovery through verified implementation, enabling end-to-end provider integration with gates.

Core Features & Use Cases

Guides end-to-end provider onboarding (discovery, design, implementation, verification) for Grafana Cloud products.
Enforces gated approvals and documentation deliverables (research, ADRs, specs, smoke tests) to ensure robust provider integration.
Leverages existing references (decision trees and guides) to validate provider scope and applicability.

Quick Start

Ask gcx to add a new Grafana Cloud provider and gcx will walk you through Discover, Design, Implement, and Verify.

Frequently Asked Questions about add-provider

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

FAQPage Schema

How do I add a new Grafana Cloud provider to gcx?▼

To add a Grafana Cloud provider to gcx, the system orchestrates an end-to-end workflow through Discover, Design, Implement, and Verify stages. It guides API discovery and verified implementation while producing research reports, ADRs, design specs, and smoke tests.

How does the gated approval process work for Grafana provider onboarding?▼

The gated approval process for Grafana provider onboarding enforces explicit user approvals before advancing between Discover, Design, Implement, and Verify stages. This ensures documentation deliverables like ADRs and design specs are validated prior to moving forward.

What documentation deliverables are required for Grafana product provider integration?▼

Grafana product provider integration requires research reports, Architecture Decision Records (ADRs), a design spec, stage-specific code, and smoke tests. These artifacts are produced throughout the Discover, Design, Implement, and Verify stages.

Can I integrate any Grafana Cloud product provider using this guided workflow?▼

You can integrate Grafana Cloud product providers such as SLO, OnCall, Synthetic Monitoring, k6, and ML. The workflow leverages existing references like decision trees and guides to validate provider scope and applicability before implementation.

What is the best way to streamline Grafana provider integrations from API discovery to implementation?▼

Streamlining Grafana provider integrations is best achieved by automating the end-to-end onboarding workflow with gated approvals. This approach manages the transition from API discovery to verified implementation while generating required artifacts like ADRs and smoke tests.

Why do I need stage-specific gates when adding a Grafana provider?▼

Stage-specific gates are needed when adding a Grafana provider to ensure robust integration and validate all documentation deliverables. They enforce explicit user approvals before moving from Discover to Design, Implement, and Verify, preventing incomplete code or missing specs.