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 better differentiate from a generic dashboard skill.
| 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 a verbose reference catalog of Grafana dashboard JSON snippets and well-known monitoring concepts (RED/USE methods, panel types) that Claude already understands. It lacks a clear end-to-end workflow for creating dashboards, has no validation steps, and includes excessive boilerplate JSON inline rather than in the referenced asset files. The content would benefit greatly from being condensed to focus on project-specific conventions and a clear creation workflow.
Suggestions
Add a clear step-by-step workflow for creating a dashboard (e.g., 1. Define metrics, 2. Create JSON, 3. Validate with Grafana API, 4. Deploy via provisioning, 5. Verify panels load data) with explicit validation checkpoints.
Remove explanations of RED/USE methods, panel type descriptions, and other concepts Claude already knows—focus only on project-specific conventions and non-obvious configuration patterns.
Move the large JSON examples into the referenced asset files (api-dashboard.json, etc.) and keep only minimal inline snippets showing key patterns or gotchas.
Provide the referenced bundle files (assets/api-dashboard.json, references/dashboard-design.md, etc.) so the progressive disclosure structure actually works.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with large JSON blocks that are mostly boilerplate Grafana configuration Claude already understands. Concepts like RED/USE methods, panel types, and basic dashboard design principles are well-known to Claude and don't need explanation. The content could be reduced by 60-70% without losing actionable value. | 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), and the 'Common Dashboard Patterns' sections only list panel names without actual PromQL queries or JSON, making them vague. | 2 / 3 |
Workflow Clarity | There is no clear sequenced workflow for creating a dashboard end-to-end. The content is a reference catalog of panel types and JSON snippets without steps like 'first do X, then Y, validate with Z.' No validation checkpoints exist—there's no mention of how to verify a dashboard JSON is valid before deploying, or how to test that queries return data. | 1 / 3 |
Progressive Disclosure | The skill references several asset files (api-dashboard.json, infrastructure-dashboard.json, etc.) and related skills, which is good structure. However, no bundle files are provided, so these references are broken. The main file itself is monolithic with too much inline JSON that should be in the referenced asset files instead. | 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
5a13356
- 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.