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, 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 reference manual than an actionable skill for Claude. It's heavily padded with concepts Claude already knows (RED/USE methods, what different panel types are), lacks any sequential workflow for dashboard creation or deployment, and has no validation steps. The JSON examples provide some value but would be better served as referenced asset files with the SKILL.md providing a concise workflow.
Suggestions
Replace the catalog-style content with a clear step-by-step workflow: 1) Define metrics to monitor, 2) Create dashboard JSON, 3) Validate JSON structure, 4) Deploy via API/provisioning, 5) Verify dashboard loads and queries return data.
Remove the RED/USE method explanations and panel type catalog — Claude already knows these. Instead, provide one complete dashboard example and reference asset files for additional templates.
Add validation checkpoints: verify dashboard JSON is valid before deploying, check that Prometheus queries return data, confirm dashboard renders correctly after provisioning.
Either provide the referenced bundle files (assets/api-dashboard.json, etc.) or remove the dead references and inline only the most essential example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with significant content Claude already knows (RED/USE methods, what panel types are, basic Grafana concepts). The dashboard design principles section explains well-known monitoring methodologies that don't need re-teaching. Many JSON examples are overly detailed with boilerplate fields. | 1 / 3 |
Actionability | The JSON examples are concrete and mostly copy-paste ready, which is good. However, there's no clear workflow for actually creating a dashboard (e.g., using the Grafana API, or where to place files). The Terraform and Ansible snippets are useful but incomplete — no connection details, no validation of deployment success. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for creating, validating, or deploying a dashboard. The content is a reference catalog of panel types and JSON snippets without any step-by-step process. No validation checkpoints exist — no mention of testing the dashboard loads correctly, verifying queries return data, or checking for errors after provisioning. | 1 / 3 |
Progressive Disclosure | References to asset files like `assets/api-dashboard.json`, `assets/infrastructure-dashboard.json`, and `assets/database-dashboard.json` are mentioned but no bundle files exist, making these dead references. The content that could be in separate files (all the panel type examples, provisioning configs) is inlined, making the SKILL.md bloated. | 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
34632bc
- 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.