jbvc/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.
65
65%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 clear 'what' and 'when' clauses, strong trigger terms centered around Grafana and monitoring, and excellent distinctiveness due to 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', such as configuring panels, setting up alerting rules, or defining data source connections.
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 makes this highly distinctive and unlikely to conflict with other skills. The combination of Grafana + dashboards + monitoring creates a clear niche. | 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 dashboard documentation page than an actionable skill for Claude. It is excessively verbose with large JSON blocks inline that should be in reference files, explains concepts Claude already knows (RED/USE methods), and critically lacks a clear step-by-step workflow for actually creating and deploying a dashboard. The generic instruction bullets at the top ('Clarify goals, constraints, and required inputs') add no value.
Suggestions
Replace the generic instruction bullets with a concrete step-by-step workflow: 1) Determine dashboard purpose and metrics, 2) Choose panel types, 3) Build JSON structure, 4) Validate with Grafana API import, 5) Verify panels render correctly.
Move the large JSON examples (panel types catalog, full dashboard JSON) into the referenced asset files and keep only a minimal example in the main skill to illustrate the pattern.
Remove explanations of RED/USE methods - Claude already knows these. Instead, just reference them as organizational patterns (e.g., 'Organize service dashboards using RED method, resource dashboards using USE method').
Add validation steps: how to verify a dashboard JSON is valid before importing, how to test that PromQL queries return data, and how to confirm alert conditions fire correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with large JSON blocks that could be referenced from external files. It explains well-known concepts like RED/USE methods that Claude already knows, includes redundant sections ("Do not use this skill when" adds no value), and the panel type catalog is essentially documentation that belongs in reference files, not the main skill. | 1 / 3 |
Actionability | The JSON examples are concrete and mostly copy-paste ready, which is good. However, the skill lacks a clear end-to-end workflow for actually creating a dashboard (e.g., how to import the JSON, how to use the Grafana API). It's more of a reference catalog than actionable guidance for completing a task. | 2 / 3 |
Workflow Clarity | There is no clear sequenced workflow for creating a dashboard from start to finish. The content is organized as a reference catalog of panel types and patterns without steps, validation checkpoints, or feedback loops. The generic instructions ('Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.') are vague and unhelpful. | 1 / 3 |
Progressive Disclosure | References to external files exist (assets/*.json, resources/implementation-playbook.md, references/dashboard-design.md) which is good, but the main file still contains massive inline JSON blocks that should be in those reference files. The skill would benefit from being a concise overview that points to the detailed examples rather than embedding them. | 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.
Reviewed
Table of Contents