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
85%
1.16xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/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 and good trigger term coverage around Grafana, monitoring, and observability. Its 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 data source connections, creating template variables).
Suggestions
Expand the capability list with more specific actions, e.g., 'configure panels, set up alert rules, define data source queries, create template variables' 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 is essentially a reference catalog of Grafana JSON configurations with no clear workflow or process guidance. It's excessively verbose, spending most of its token budget on boilerplate JSON that Claude could generate from minimal prompts, while lacking the operational workflow (create → validate → deploy → verify) that would make it truly useful. The content would benefit greatly from being restructured as a lean overview with linked reference files.
Suggestions
Add a clear step-by-step workflow for dashboard creation: design → create JSON → validate schema → provision → verify in Grafana UI, with explicit validation checkpoints at each stage.
Move the extensive JSON panel examples into a separate reference file (e.g., PANEL_REFERENCE.md) and keep only one concise example in the main skill file.
Remove sections Claude already knows (RED/USE method definitions, 'What is a stat panel', basic best practices like 'use consistent naming') and focus on non-obvious Grafana-specific gotchas and patterns.
Add concrete validation steps such as how to validate dashboard JSON schema, test variable queries, and verify alert conditions before deploying to production.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive JSON examples that are largely boilerplate. The RED/USE method explanations, 'Purpose' and 'When to Use' sections, and best practices list are all things Claude already knows. The dashboard design principles section explains basic concepts unnecessarily. Much of this could be condensed to key patterns and non-obvious configuration details. | 1 / 3 |
Actionability | The JSON examples are concrete and mostly copy-paste ready, which is good. However, many are incomplete dashboard fragments rather than fully executable configurations, and references to asset files (e.g., 'See assets/api-dashboard.json') point to resources that may not exist. The examples cover panel types well but lack context on how to actually deploy or validate a dashboard end-to-end. | 2 / 3 |
Workflow Clarity | There is no clear workflow for creating a dashboard from start to finish. The content is a reference catalog of panel types and configurations without sequencing, validation steps, or feedback loops. For a skill involving production dashboard deployment, there should be explicit steps for creating, validating, testing, and deploying dashboards. | 1 / 3 |
Progressive Disclosure | There are references to external files (asset JSONs, related skills) which is good, but the main file itself is a monolithic wall of JSON examples that should be split into separate reference files. The panel type catalog and full dashboard JSON examples would be better as linked references, keeping the SKILL.md as a concise overview. | 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
- wshobson/agents
- Commit
27a7ed9
- 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.