Name: grafana-dashboards
Rating: 50.4 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

grafana-dashboards

Create and manage production-ready Grafana dashboards for comprehensive system observability.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/grafana-dashboards/SKILL.md

The canonical home for this skill is grafana-dashboards in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, actionable reference catalog of executable Grafana dashboard examples, but it is padded with generic boilerplate, lacks a concrete sequenced workflow with validation, and relies on bundle files that do not exist. Tightening the filler, adding a verified workflow, and supplying the missing referenced files would meaningfully raise quality.

Suggestions

Remove the generic "Do not use this skill when" and "Instructions" boilerplate, or replace with Grafana-specific guidance (e.g. when to use RED vs USE, how to choose panel types).

Add a concrete sequenced dashboard-creation workflow with a validation checkpoint, e.g. define panels -> validate JSON -> provision -> verify in Grafana UI.

Create the missing referenced files (assets/api-dashboard.json, assets/infrastructure-dashboard.json, assets/database-dashboard.json, references/dashboard-design.md, resources/implementation-playbook.md) and move the inlined JSON blocks into them so progressive disclosure is functional.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code blocks, but generic boilerplate ("Do not use this skill when: The task is unrelated to grafana dashboards", "Clarify goals, constraints...", "Apply relevant best practices and validate outcomes") and a Purpose section that restates the description add padding that could be trimmed.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready JSON dashboards, PromQL expressions, panel configs, and Terraform/Ansible provisioning; minor gaps exist where "Common Dashboard Patterns" sections list only "Key Panels" without executable code.	4 / 5
Workflow Clarity	There is no real sequenced dashboard-creation workflow; the only "Instructions" are generic with no validation checkpoints, and dashboard provisioning (a batch operation) lacks any verify step, so workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Section headers are clear and references are explicitly signaled, but every referenced bundle file (assets/*.json, references/dashboard-design.md, resources/implementation-playbook.md) is missing on disk, and large JSON blocks that belong in those files are inlined, so the disclosure structure is incomplete.	3 / 5
	Total	13 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names a clear domain and two actions but leans on generic verbs and buzzword filler, and it omits any explicit "Use when..." trigger guidance. Adding concrete trigger phrases and a few more specific actions would lift it from mid-range to strong.

Suggestions

Add an explicit "Use when..." clause listing concrete triggers, e.g. "Use when creating or editing Grafana dashboards, adding panels or alert rules, or provisioning dashboards as code."

Replace generic "manage" with specific actions like "configure panels, templating variables, and alert rules" to raise specificity.

Swap "comprehensive system observability" buzzword filler for natural synonyms users actually say (monitoring dashboards, metrics visualization, Prometheus/Grafana dashboards).

Dimension	Reasoning	Score
Specificity	"Create and manage production-ready Grafana dashboards" names the domain plus two actions, but "manage" is generic and "comprehensive system observability" is buzzword filler; it does not list several specific concrete actions (alerts, variables, provisioning) needed for a 4.	3 / 5
Completeness	It clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	"Grafana dashboards" and "system observability" are relevant keywords a user might say, but common variations and synonyms ("monitoring dashboards", "metrics visualization", "Prometheus dashboards") are missing.	3 / 5
Distinctiveness Conflict Risk	"Grafana dashboards" is a clear, distinct niche with minimal conflict risk, but the broad phrase "comprehensive system observability" leaves minor overlap with related prometheus/slo skills, keeping it just below a 5.	4 / 5
	Total	13 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/grafana-dashboards/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.