
Import Dashboards
- 4 installs
- 524 repo stars
- Updated August 4, 2026
- grafana/gcx
import-dashboards skill documents Use when the user wants to import existing Grafana dashboards as Go code, convert live dashboards to builder code, migrate dashboards to code, or reverse-engineer a dashboard from a Graf
About
import-dashboards skill documents Use when the user wants to import existing Grafana dashboards as Go code, convert live dashboards to builder code, migrate dashboards to code, or reverse-engineer a dashboard from a Grafana instance. Triggers on "import dashboard", "convert to code", "dashboard as code", "export dashboard".. name: import-dashboards description: >
- Use when the user wants to import existing Grafana dashboards as Go code, convert live dashboards to builder code, migra
- Platform-specific setup patterns for import-dashboards.
- Evidence-backed steps from upstream SKILL.md.
- When-to-use criteria for import-dashboards versus alternatives.
Import Dashboards by the numbers
- 4 all-time installs (skills.sh)
- Ranked #1,101 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
import-dashboards capabilities & compatibility
- Capabilities
- import dashboards quick start · import dashboards when to use guidance · import dashboards integration patterns
- Works with
- grafana
What import-dashboards says it does
Use when the user wants to import existing Grafana dashboards as Go code,
convert live dashboards to builder code, migrate dashboards to code,
npx skills add https://github.com/grafana/gcx --skill import-dashboardsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4 |
|---|---|
| repo stars | ★ 524 |
| Last updated | August 4, 2026 |
| Repository | grafana/gcx ↗ |
How do I use import-dashboards correctly?
Use when the user wants to import existing Grafana dashboards as Go code, convert live dashboards to builder code, migrate dashboards to code, or reverse-engineer a dashboard from a Grafana instance.
Who is it for?
Teams implementing import-dashboards workflows from the catalog.
Skip if: Skip when requirements clearly match a different specialized stack.
When should I use this skill?
User asks about import-dashboards, use when the user wants to import existing grafana dashboards as go code, convert live das.
What you get
Working import-dashboards setup with validated configuration and next steps.
Files
Import Dashboards as Code
Import existing dashboards from a Grafana instance and convert them to Go builder code using gcx dev import.
Prerequisites
1. gcx installed and configured with a Grafana connection (gcx config check should show a valid context) 2. The target Grafana instance must be reachable
Import Commands
Import All Dashboards
gcx dev import dashboardsWrites Go files to imported/ (default). Each dashboard becomes a function returning *resource.ManifestBuilder.
Import a Specific Dashboard
gcx dev import dashboards/my-dashboard-uidImport to a Custom Directory
gcx dev import dashboards --path src/grafanaImport Multiple Resource Types
gcx dev import dashboards foldersHow It Works
Grafana Instance
│
▼
gcx dev import dashboards/foo
│
├── 1. Fetches resource via K8s API (/apis endpoint)
├── 2. Detects API version (v0alpha1, v1beta1, v2beta1)
├── 3. Runs version-specific converter (JSON → SDK builder code)
├── 4. Wraps in resource.NewManifestBuilder()
└── 5. Writes to imported/<snake_case_name>.goThe converter produces Go code using the grafana-foundation-sdk builder pattern — the same pattern used by dev generate and dev scaffold.
Output Format
Each imported file looks like:
package dashboards
import (
"github.com/grafana/grafana-foundation-sdk/go/dashboardv2beta1"
"github.com/grafana/grafana-foundation-sdk/go/resource"
)
func MyDashboard() *resource.ManifestBuilder {
// ... builder code generated from the live dashboard
}Workflow: Import → Edit → Push
# 1. Import from Grafana
gcx dev import dashboards --path internal/dashboards
# 2. Review and edit the generated code
# (fix up builder calls, add variables, etc.)
# 3. Push back to Grafana
gcx resources pushCommon Issues
| Issue | Fix |
|---|---|
| "no converter found" | Dashboard uses an unsupported API version; only v0alpha1, v1beta1, v2beta1 supported |
| Auth error (401/403) | Run gcx config check to verify credentials |
| Empty import | The selector matched no resources; check UID with gcx resources get dashboards |
| Imported code doesn't compile | Some complex dashboards produce converter output that needs manual fixup |
Related skills
FAQ
What does import-dashboards do?
import-dashboards skill documents Use when the user wants to import existing Grafana dashboards as Go code, convert live dashboards to builder code, migrate dashboards to code, or reverse-engineer a dashboard from a Grafana instance.
When should I use import-dashboards?
User asks about import-dashboards, use when the user wants to import existing grafana dashboards as go code, convert live das.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.