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

Blog Docs Log in Get started

grafana-dashboards

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

Quality

57%

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/skills/grafana-dashboards/SKILL.md

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

Quality

Content

61%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 content is highly actionable with strong copy-paste examples, but it lacks a concrete sequenced workflow with validation checkpoints and suffers from broken progressive-disclosure references to non-existent bundle files. Tightening redundancy and supplying the referenced files would materially improve it.

Suggestions

Create the referenced bundle files (assets/api-dashboard.json, assets/infrastructure-dashboard.json, assets/database-dashboard.json, references/dashboard-design.md, resources/implementation-playbook.md) or remove the references.

Replace the generic Instructions with a concrete sequenced workflow including a validation checkpoint (e.g. validate dashboard JSON with grafana-cli or a linter before provisioning).

Move the full inlined dashboard JSON into the asset files and keep only a concise representative panel example inline to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete JSON examples, but full dashboard JSON is inlined while the same dashboards are also referenced as asset files, and the generic Instructions/Purpose/Use-when sections add bulk that could be tightened — matching anchor 3; not anchor 4 because the redundancy is more than minor.	3 / 5
Actionability	Provides copy-paste-ready JSON, HCL, and YAML examples covering the common cases (API dashboard, stat/time-series/table/heatmap panels, variables, alerts, provisioning, Terraform, Ansible), matching anchor 5; the bullet-only pattern sections are minor and do not pull it below anchor 4.	5 / 5
Workflow Clarity	The Instructions give a rough sequence (clarify goals → apply best practices → validate outcomes) but validation is only implicit with no concrete checkpoints or feedback loop, matching anchor 3; not anchor 2 because a sequence and a nod to validation exist, and not anchor 4 because checkpoints are missing.	3 / 5
Progressive Disclosure	The body references assets/*.json, references/dashboard-design.md, and resources/implementation-playbook.md, but no bundle directories exist, so these are broken references, and full dashboard JSON that belongs in separate files is inlined — matching anchor 2; not anchor 3 because broken references make navigation worse than merely unclear signaling.	2 / 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 clearly states what the skill does and targets a distinct niche, but it omits any explicit "Use when..." trigger guidance and has limited keyword coverage. Adding concrete trigger phrases would raise completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause listing natural triggers (e.g. 'Use when creating Grafana dashboards, visualizing Prometheus metrics, or building SLO/monitoring dashboards').

Add common synonyms users say — monitoring, metrics, panels, .json dashboard files — to broaden trigger-term coverage.

Expand the action list beyond 'create and manage' to specifics like 'design, provision, and alert on dashboards' for fuller specificity.

Dimension	Reasoning	Score
Specificity	Quotes "Create and manage production-ready Grafana dashboards" — names the domain plus two concrete actions (create, manage), matching anchor 3; not anchor 4 because only two actions are listed rather than several, and not anchor 2 because domain and actions are both present.	3 / 5
Completeness	The "what" is clear (create and manage Grafana dashboards) but there is no "Use when..." trigger clause, and the rubric caps completeness at 3 when explicit trigger guidance is missing; below anchor 4 which requires both what and when.	3 / 5
Trigger Term Quality	"Grafana dashboards" and "system observability" are relevant natural terms, but common variations such as monitoring, metrics, or panels are absent, matching anchor 3; below anchor 4 which expects good coverage with only a few terms missing.	3 / 5
Distinctiveness Conflict Risk	"Grafana dashboards" names a clear, product-specific niche with only minor overlap risk against closely related monitoring skills (e.g. Prometheus, SLO), matching anchor 4; not anchor 5 because no distinct trigger phrases are given.	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/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.