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.
85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 skill description with explicit 'Use when' guidance and good trigger term coverage. The main weakness is that the capability description could be more specific about concrete actions beyond 'create and manage'. The Grafana-specific focus provides good distinctiveness.
Suggestions
Expand specificity by listing concrete actions like 'configure panels, set up alerting rules, create template variables, define PromQL/LogQL queries'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Grafana dashboards) and mentions some actions ('create and manage', 'real-time visualization'), but lacks comprehensive specific actions like 'configure panels', 'set up alerts', 'create variables', or 'define queries'. | 2 / 3 |
Completeness | Clearly answers both what ('Create and manage production Grafana dashboards for real-time visualization') and when ('Use when building monitoring dashboards, visualizing metrics, or creating operational observability interfaces') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Grafana', 'dashboards', 'monitoring', 'metrics', 'visualization', 'observability'. These are terms users naturally use when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with 'Grafana' as a distinct identifier. Unlikely to conflict with generic monitoring or visualization skills due to the specific tool mention and domain-specific terms like 'observability interfaces'. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent concrete JSON examples for Grafana dashboard configuration. The main weaknesses are some unnecessary introductory content and missing validation workflows for testing dashboards before deployment. The progressive disclosure and actionability are strong points.
Suggestions
Remove or condense the 'Purpose' and 'When to Use' sections - Claude understands when to use Grafana dashboards
Add a validation workflow section: how to test queries in Explore before adding to dashboards, how to verify dashboard loads correctly, and how to validate JSON syntax before provisioning
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanatory content like the 'Purpose' and 'When to Use' sections that Claude doesn't need. The RED/USE method explanations are borderline - useful context but could be more terse. | 2 / 3 |
Actionability | Excellent executable JSON examples for all panel types, complete with PromQL queries, grid positioning, and alert configurations. The Terraform and Ansible provisioning examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill provides good structural guidance (hierarchy diagram, panel types) but lacks explicit validation steps. There's no workflow for testing dashboards before deployment or verifying that queries return expected data. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, references to external JSON files (assets/api-dashboard.json, etc.), and links to related skills. The structure moves from principles to examples to provisioning logically. | 3 / 3 |
Total | 10 / 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.
- 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.