debug-with-grafana
grafana/gcxStructured workflow for investigating application problems with Grafana observability data (metrics, logs, traces) via gcx. Covers live firefighting AND…
Scores out of 100 · grade A
2026-08-13Works
40% of the score100/100
- Loads cleanly: valid frontmatter, required fields present, no dangling references.
Maintained
25% of the score100/100
- no commits in the last 12 weeks
Adopted
20% of the score38/100
- 550 stars on the source repo.
Documented
15% of the score90/100
- 2,162 words with worked examples.
- Ships 4 bundled files.
Install
npx skills add grafana/gcx/debug-with-grafanaWhat it says it does
Structured workflow for investigating application problems with Grafana observability data (metrics, logs, traces) via gcx. Covers live firefighting AND retrospective incident analysis: incident triage, root-cause analysis, blast-radius checks (did an incident spill into other services), verifying whether a deployment or rollout triggered an incident, finding which service, endpoint, or path owns the most errors or slow requests, checking whether retries or queue backlogs piled up, and quantifying error or latency shares over a time window. Trigger on: "my API is returning 500 errors", "latency is spiking", "investigate why requests are failing", "triage the incident", "blast radius", "root cause", "did the rollout cause it", "which endpoint owns the most 5xx", "did retries pile up", or any request to analyse an earlier incident window using telemetry. For authoring dashboards use create-dashboard; for dashboard inventory use manage-dashboards.
Also in grafana/gcx
| Artifact | Score | What the check found | Type | Reach | Last commit |
|---|---|---|---|---|---|
| integrate-with-gcxgrafana/gcx | clean | Skill | 550 stars | today | |
| agento11ygrafana/gcx | clean | Skill | 550 stars | today | |
| investigate-alertgrafana/gcx | clean | Skill | 550 stars | today | |
| manage-dashboardsgrafana/gcx | clean | Skill | 550 stars | today | |
| setup-gcxgrafana/gcx | clean | Skill | 550 stars | today | |
| slo-investigategrafana/gcx | clean | Skill | 550 stars | today |
Other debugging skills
Browse all| Artifact | Score | What the check found | Category | Reach | Last commit |
|---|---|---|---|---|---|
| azure-diagnosticsmicrosoft/azure-skills | clean | Debugging | 538,931 installs | today | |
| diagnosing-bugsmattpocock/skills | clean | Debugging | 446,167 installs | today | |
| draft-responseanthropics/knowledge-work-plugins | clean | Debugging | 2,281 installs | today | |
| debuganthropics/knowledge-work-plugins | clean | Debugging | 5,114 installs | today | |
| fix-ci-failuresmicrosoft/vscode | clean | Debugging | 189k stars | today | |
| sweeper-fixmicrosoft/vscode | clean | Debugging | 189k stars | today |
Put this measurement in your README
A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
[](https://skillworks.kynth.studio/?q=grafana%2Fgcx)Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.
