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 explicit 'Use when' guidance and good trigger term coverage. Its main weakness is that the capability listing is somewhat general—'create and manage' could be more specific about concrete actions like configuring panels, setting up alerting rules, or defining data source queries. Overall it performs well for skill selection purposes.
Suggestions
Expand the 'what' portion with more specific concrete actions, e.g., 'configure panels, set up alert rules, define queries against Prometheus/InfluxDB data sources, create template variables'.
| 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, or defining data sources. | 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). | 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 | Clearly scoped to Grafana dashboards specifically, with distinct triggers like 'Grafana', 'monitoring dashboards', and 'observability interfaces' that are unlikely to conflict with other skills. | 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 bloated with JSON boilerplate, explains concepts Claude already knows (RED/USE methods, what panel types are), and critically lacks any workflow for actually creating and deploying dashboards. The content would benefit greatly from being condensed to essential patterns with clear step-by-step workflows and actual bundle files for the referenced assets.
Suggestions
Add a clear end-to-end workflow: design → create JSON → validate schema → provision → verify dashboard loads correctly, with explicit validation checkpoints at each stage.
Move the panel type JSON examples into a referenced file (e.g., references/panel-types.md) and keep only one representative example inline to dramatically reduce token usage.
Remove explanations of RED/USE methods and basic Grafana concepts that Claude already knows; replace with project-specific conventions or constraints.
Provide the referenced bundle files (assets/api-dashboard.json, etc.) or remove the references to avoid hollow pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with significant redundancy. It explains basic concepts like RED/USE methods that Claude already knows, lists obvious best practices ('use consistent naming'), and includes multiple panel type examples that are largely boilerplate JSON. The 'When to Use' and 'Purpose' sections are redundant with each other and the description. | 1 / 3 |
Actionability | The JSON examples are concrete and mostly copy-paste ready, which is good. However, they're incomplete dashboard definitions (missing required fields like uid, version, schemaVersion), and there's no guidance on how to actually deploy or validate these dashboards. The Terraform and Ansible snippets are useful but minimal. | 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 JSON snippets without sequencing, validation steps, or feedback loops. For a skill involving production dashboard deployment, there should be explicit steps: create → validate → provision → verify. | 1 / 3 |
Progressive Disclosure | References to asset files (api-dashboard.json, infrastructure-dashboard.json, etc.) and related skills are well-signaled and one level deep. However, no bundle files actually exist, making these references hollow. The main file itself contains too much inline content (all panel type examples, full JSON blocks) that should be in referenced files. | 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
bbc5ade
- 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.