grafana-dashboards

Create and manage production Grafana dashboards for real-time visualization of system and application metrics. Use when building monitoring dashboards, visualizing metrics, or creating operational observability interfaces.

1.17x

Quality

74%

Does it follow best practices?

Impact

86%

1.17x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/observability-monitoring/skills/grafana-dashboards/SKILL.md

The canonical home for this skill is grafana-dashboards in wshobson/agents

Quality

Content

65%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 a strong, code-heavy reference catalog with mostly copy-paste-ready examples across panels, templating, alerts, and provisioning. Its weaknesses are the absence of an explicit build/validate workflow and references to asset/reference files that are not present in the bundle.

Suggestions

Add an explicit dashboard authoring workflow with validation checkpoints (e.g. draft JSON -> validate with grafana-cli or `grr` -> provision -> verify in UI).

Provide the referenced bundle files (assets/api-dashboard.json, assets/infrastructure-dashboard.json, assets/database-dashboard.json, references/dashboard-design.md) or remove the broken references and keep the key examples inline.

Either flesh out the "Common Dashboard Patterns" sections with concrete code or move their full definitions into the asset files they point to.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, copy-paste JSON/YAML/HCL snippets rather than prose, but the redundant "Purpose" section and brief re-explanation of known concepts (RED/USE methods) are minor over-explanation that could be trimmed.	4 / 5
Actionability	Concrete executable examples cover panels, templating variables, alerts, provisioning, and IaC, but the "Common Dashboard Patterns" sections are only bullet lists of panel names and the referenced asset files do not exist, leaving minor gaps.	4 / 5
Workflow Clarity	Content is organized by topic (design, panel types, variables, alerts, provisioning) rather than as an explicit sequenced workflow, and no validation/verification checkpoints are given for building or deploying a dashboard.	3 / 5
Progressive Disclosure	Section structure is reasonable and references are clearly signaled ("Reference: See `assets/...`"), but the referenced `assets/` and `references/` files do not exist, and large dashboard JSON blocks are inlined that would better live in separate files.	3 / 5
	Total	14 / 20 Passed

Description

83%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 is strong: it concisely states concrete capabilities and provides an explicit, multi-trigger "Use when" clause that answers both what and when. Its main weakness is broad observability triggers that could overlap with adjacent monitoring skills.

Suggestions

Tighten triggers to Grafana-specific phrasing (e.g. "Grafana dashboards", "Grafana panels", ".json dashboard models") to reduce overlap with prometheus/slo skills.

Consider naming one or two more concrete actions (e.g. "configure alerts and templating variables", "provision dashboards as code") to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Create and manage production Grafana dashboards for real-time visualization of system and application metrics" names the domain plus several concrete actions (create, manage, visualize), matching the anchor that lists several specific actions with minor coverage gaps.	4 / 5
Completeness	It explicitly answers both "what" (create and manage Grafana dashboards for real-time visualization) and "when" with concrete trigger phrases in an explicit "Use when..." clause, matching the top anchor.	5 / 5
Trigger Term Quality	The "Use when" clause supplies natural phrases users would say ("building monitoring dashboards", "visualizing metrics", "observability interfaces"), giving good keyword coverage, but it omits synonyms and file-extension terms that would reach comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	"Production Grafana dashboards" is a distinct, tool-specific niche, but broad triggers like "visualizing metrics" and "observability" overlap with closely related monitoring skills (e.g. prometheus-configuration, slo-implementation listed in the body), so it is mostly distinct with minor overlap risk.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/observability-monitoring/skills/grafana-dashboards/SKILL.md
Commit: 6453c0b

Reviewed: about 8 hours 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.