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

66%

Does it follow best practices?

Impact

86%

1.17x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

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

53%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 delivers concrete, largely executable Grafana dashboard examples and provisioning configs, but it functions as a reference catalog rather than a guided workflow, and every referenced bundle file is missing from the skill directory. Trimming the introductory design-method explanations and fixing (or removing) the dangling file references would substantially improve it.

Suggestions

Create the referenced bundle files (assets/api-dashboard.json, assets/infrastructure-dashboard.json, assets/database-dashboard.json, references/dashboard-design.md) or remove the 'Reference:'/'Reference Files' mentions, since all currently point to nonexistent paths.

Add a stepwise dashboard delivery workflow with validation, e.g., 1. identify metrics, 2. choose panel types, 3. write dashboard JSON, 4. validate against the Grafana API, 5. provision and verify — replacing the current catalog-style layout.

Cut the 'Dashboard Design Principles' section's explanations of RED/USE and the ASCII hierarchy diagram, which restate knowledge Claude already has, and move full dashboard JSON into the asset files to slim the body.

Dimension	Reasoning	Score
Conciseness	The 'Dashboard Design Principles' section explains RED/USE methods and an ASCII information hierarchy — concepts Claude already knows — and inline panel JSON partially duplicates content claimed to exist in asset files. Most sections are concrete, so this is tighter than anchor 2 but noticeably trimmable.	3 / 5
Actionability	Concrete PromQL expressions, a complete dashboard JSON example, and executable Terraform/Ansible/dashboards.yml provisioning configs provide mostly executable guidance. Falls short of anchor 5 because panel snippets omit datasource context and there is no command to actually load or verify a dashboard (e.g., via the Grafana API).	4 / 5
Workflow Clarity	Content is organized as a catalog (principles, examples, provisioning) with no ordered steps for building and deploying a dashboard, and no validation checkpoints confirming a dashboard JSON loads correctly before or after provisioning. A rough conceptual ordering exists, keeping it above anchor 2.	3 / 5
Progressive Disclosure	The body references 'assets/api-dashboard.json', 'assets/infrastructure-dashboard.json', 'assets/database-dashboard.json', and 'references/dashboard-design.md', but no references/, scripts/, or assets/ directories exist — every pointer is broken. Combined with large dashboard JSON inlined in the body, navigation to deeper material fails entirely, matching anchor 2 rather than 3.	2 / 5
	Total	12 / 20 Passed

Description

78%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.

A strong description that clearly and explicitly states both capability and trigger conditions in third person with concrete, natural language. The main gaps are modest: slightly thin action coverage in the what-clause and one overly broad trigger term.

Dimension	Reasoning	Score
Specificity	Names the domain ('production Grafana dashboards') with 2-3 concrete actions ('Create and manage', 'real-time visualization'), but coverage is not comprehensive — variables, alerting, and provisioning capabilities are absent from the description.	3 / 5
Completeness	Explicitly answers both: what ('Create and manage production Grafana dashboards for real-time visualization of system and application metrics') and when ('Use when building monitoring dashboards, visualizing metrics, or creating operational observability interfaces') with concrete trigger phrases.	5 / 5
Trigger Term Quality	'building monitoring dashboards', 'visualizing metrics', and 'operational observability interfaces' are natural user phrases with 'Grafana' anchoring the domain, but common variations like 'graphs', 'panels', or 'metrics dashboard' are missing.	4 / 5
Distinctiveness Conflict Risk	'Grafana dashboards' carves a clear niche, but the broad trigger 'visualizing metrics' creates minor overlap risk with generic metrics or dataviz skills rather than minimal conflict.	4 / 5
	Total	16 / 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: a65ce00

Reviewed: 6 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.