grafana-dashboards
Skill6 starsChanged 25 days agoNo licenceView on GitHub
Which Grafana panels to build from an app's structured log events, and their LogQL over Loki — HTTP traffic (status codes, endpoints, outbound errors), importer/cronjob (runs, items, error rate per pipeline, run_id trace lookup) and outbound webhook deliveries — plus the template variables they share and where the dashboard JSON lives in the app repo (`docs/dashboards/grafana-dashboard.json`). Use when adding or changing a dashboard panel, or when asked "put this on a dashboard". Invoke as /grafana-dashboards [app] [what to add].
14 other projects use a version of this.
Adopted by
Most recently taken up by
- ControllableModel/SWE-Skills-Benchtheir own version, first seen Nov 8, 2026
- PixiBixi/claude-skillstheir own version, first seen Oct 25, 2026
- kaynetik/skillstheir own version, first seen Oct 20, 2026
- abevz/devops-skillstheir own version, first seen Oct 15, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- Samueladewole/claude-skillstheir own version, first seen Oct 13, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- hardisgroupcom/sfdx-hardis★ 432same name
- xfstudio/skills★ 9same name
- ControllableModel/SWE-Skills-Bench★ 8same name
- ai4brands-design/claude-skills★ 2same name
- CodeWithBehnam/cc-docs★ 2same name
- Ghosteken/agent-harness★ 2same name
- cvsz/zomega★ 1same name
- ElyzeSolutions/skills★ 1same name
- kaynetik/skills★ 1same name
- smk-labs/claude-config★ 1same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- acceptance-criteriaSkill
- app-designSkill
- ci-cdSkill
- credentialsSkill
- definition-of-readySkill
- feature-flagsSkill
- gate-policiesSkill
- gitflowSkill
- kubectlSkill
- observabilitySkill
- pull-requestSkill
- refinement-contextSkill
- rollout-planSkill
- secret-or-settingSkill
- skill-designSkill
- task-trackerSkill
- test-appsSkill
- ticket-lifecycleSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.