migrate-provider

Port Grafana Cloud resources from grafana-cloud-cli into a gcx provider.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Porting Grafana Cloud resources from grafana-cloud-cli (gcx) to gcx is a complex, error-prone process that benefits from a structured, phase-gated orchestration.

Core Features & Use Cases

  • Phase-driven migration workflow (Phase 0–Phase 4) for porting gcx resources to providers.
  • ADR-based design discovery and documentation (docs/adrs/{provider}/).
  • Phase 2 spec planning with plan.md and tasks.md, including an HTTP client reference.
  • Explicit phase gates and a centralized recipe that updates gcx-provider-recipe.md.

Quick Start

Initiate the migration workflow by following Phase 0 through Phase 4 as described.

Frequently Asked Questions about migrate-provider

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

FAQPage Schema
How do I migrate Grafana Cloud resources from gcx to a provider?

Migrate Grafana Cloud resources from grafana-cloud-cli (gcx) to a gcx provider by following a structured five-phase orchestration workflow from Phase 0 through Phase 4, ensuring verifiable migration gates.

What is the five-phase orchestration workflow for porting gcx resources?

The five-phase orchestration for porting gcx resources spans Phase 0 initiation, Phase 1 ADR-driven design, Phase 2 spec planning, Phase 3 build and wiring, and Phase 4 verification, enforcing explicit phase gates throughout the migration.

How do I plan a gcx provider migration spec in Phase 2?

Plan a gcx provider migration spec in Phase 2 by generating a plan.md and tasks.md file that includes an HTTP client reference, serving as the blueprint for the subsequent Phase 3 build and wiring process.

Does the gcx migration workflow require Architecture Decision Records?

Yes, the gcx migration workflow requires ADR-based design discovery and documentation stored in the docs/adrs/{provider}/ directory to drive the structured design phase before spec planning begins.

What documentation needs updating when porting a Grafana Cloud resource client?

When porting a Grafana Cloud resource client, you must update the centralized gcx-provider-recipe.md file during the phase-gated workflow to maintain a verifiable migration record across all phases.

Why do I need phase gates for a Grafana Cloud provider migration?

Phase gates are needed for Grafana Cloud provider migrations because porting from grafana-cloud-cli to gcx is a complex, error-prone process that requires verifiable checkpoints to ensure each phase completes successfully before advancing.