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.
69
56%
Does it follow best practices?
Impact
86%
1.17xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/observability-monitoring/skills/grafana-dashboards/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with clear 'what' and 'when' clauses, good trigger terms covering natural user language, and strong distinctiveness through the Grafana-specific focus. The main weakness is that the specificity of capabilities could be improved by listing more concrete actions beyond 'create and manage' (e.g., configuring panels, setting up alerting rules, defining template variables, connecting data sources).
Suggestions
Expand the capability list with more specific actions, e.g., 'configure panels, set up alert rules, define template variables, connect data sources' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Grafana dashboards) and some actions ('create and manage production Grafana dashboards'), but doesn't list multiple specific concrete actions like configuring panels, setting up alerts, creating variables/templates, or defining data source queries. | 2 / 3 |
Completeness | Clearly 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 an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Grafana', 'dashboards', 'monitoring', 'metrics', 'visualization', 'observability'. These cover the main terms a user would naturally use when requesting this kind of work. | 3 / 3 |
Distinctiveness Conflict Risk | The mention of 'Grafana' specifically, combined with 'monitoring dashboards' and 'observability', creates a clear niche that is unlikely to conflict with other skills. It's distinctly about Grafana dashboard creation rather than generic data visualization or other monitoring tools. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a Grafana documentation page than an actionable skill for Claude. It spends most of its token budget on JSON panel examples and conceptual explanations (RED/USE methods, best practices) that Claude already knows, while lacking a clear step-by-step workflow for actually creating and validating dashboards. The content would benefit greatly from being restructured into a lean workflow with references to detailed examples in separate files.
Suggestions
Replace the catalog of panel type JSON examples with a concise workflow: 1) determine dashboard purpose, 2) select method (RED/USE), 3) create dashboard JSON, 4) validate via API or provisioning, 5) verify panels render correctly. Move detailed JSON examples to referenced asset files.
Remove explanations of RED/USE methods, dashboard design principles, and best practices that Claude already knows—or reduce them to a single-line reminder each.
Add explicit validation steps: how to verify a dashboard JSON is valid (e.g., Grafana API import endpoint, curl command to test), and what to do if panels show 'No data'.
Move the panel type catalog and common dashboard patterns into a separate reference file (e.g., references/panel-types.md) and link to it from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with large JSON blocks that Claude could generate on its own. The 'Purpose', 'When to Use', RED/USE method explanations, and best practices list are all things Claude already knows well. The panel type catalog reads like documentation rather than a skill. | 1 / 3 |
Actionability | The JSON examples are concrete and mostly copy-paste ready, which is good. However, much of the content describes patterns rather than instructing specific actions—listing 'Key Panels' without actual queries for infrastructure/database dashboards, and referencing asset files that may not exist. | 2 / 3 |
Workflow Clarity | There is no clear workflow for creating a dashboard end-to-end. The content is a reference catalog of panel types and patterns without sequenced steps, validation checkpoints, or feedback loops. No guidance on how to verify a dashboard works correctly after creation. | 1 / 3 |
Progressive Disclosure | References to external files (assets/*.json, references/dashboard-design.md) are present and clearly listed at the bottom. However, the main file is a monolithic wall of JSON examples that should be split into separate reference files, with only the essential workflow and key patterns kept in the SKILL.md. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- Reviewed
Table of Contents
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.