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.
Borrowing it
Nothing to install: this file belongs to grafana/gcx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/grafana/gcx/main/.claude/skills/migrate-provider/SKILL.mdgit clone --depth 1 https://github.com/grafana/gcxWrote 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.
[](https://agentmods.dev/skills/grafana/gcx/migrate-provider)<a href="https://agentmods.dev/skills/grafana/gcx/migrate-provider"><img src="https://agentmods.dev/badge/skills/grafana/gcx/migrate-provider.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00127 | $0.04231 |
| Opus 5 | $0.00063 | $0.02116 |
| Sonnet 5 | $0.00025 | $0.00846 |
| Haiku 4.5 | $0.00013 | $0.00423 |
Grade A, and why
migrate-provider 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate a Provider from the Legacy CLI
Port an existing grafana-cloud-cli resource client into this repository's gcx
provider system — core adapter, schema/example registration, CRUD redirect
commands, and ancillary subcommands.
Read this before the recipe. A human drives this skill; it is not covered by the integrate-with-gcx v1 workflow. In these instructions, "legacy CLI" means
grafana-cloud-cli, whose binary was also namedgcx; "gcx" means this repository'sbin/gcx. Usebin/gcxfor the build under review, and name the legacy binary's own path explicitly.Of the recipe's mechanical steps, only the registration flow (
providers.Register()+TypedRegistrations(), and theTypedCRUDDescriptor/Aliasesfields) has been checked against current code. Treat the rest as unaudited and verify as you go.
Before starting: read gcx-provider-recipe.md front to back for the
mechanical steps, subject to the caveat above. This skill wraps it with workflow
discipline and orchestration.
Canonical reference: the incidents_*.go files in
internal/providers/irm/ — the first full port
(adapter + schema + commands + ancillary). Start there for patterns.
When to Use
- Porting a legacy
grafana-cloud-cliresource client into current gcx - A bead task references legacy provider migration
- User says "migrate provider", "port from gcx", "port oncall", "port k6"
When NOT to use: Building a provider from scratch for a product without
a legacy CLI client — use /add-provider instead.
Relationship to integrate-with-gcx
One-directional, so the two skills cannot bounce a port back and forth:
- Recheck placement before porting. A legacy client proves that an API
existed; it does not prove that the provider tier is still the right home.
Check current
/apisCRUD coverage and inventory the non-CRUD operations. A human confirms provider-tier placement before Phases 0-4 continue. integrate-with-gcxdoes not route work here, because of the status note above: it tells the user a port needs a human to drive and stops. Reach this skill by invoking it deliberately.- Call back into two sections only, not the whole skill: the naming pass on
the ported command surface (
self-review.mdT7 — released names are frozen, and a port is where a legacy name most often gets carried in), and the diff-triggered review before requesting human review (self-review.md). Contract worksheets and the general readiness workflow do not apply to a port; the placement recheck above is still required. - Read from the checkout at
.claude/skills/integrate-with-gcx/references/self-review.md, which carries T7 and the trigger table.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed 85cbc31ee4fc
- 8d ago First seen · 420 lines · 127 tokens per session scan A dc0d5abd76f6
migrate-provider is a skill published in the GitHub repository grafana/gcx (589 stars, last pushed today), licensed Apache-2.0. It adds 127 tokens to every session and 4,231 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.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…