CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

81

1.16x
Quality

76%

Does it follow best practices?

Impact

85%

1.16x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/observability-monitoring/skills/grafana-dashboards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with extensive executable examples, but it functions as an inlined catalog rather than a lean overview pointing to reference files, and its signaled asset references are missing. Adding a build/deploy workflow with validation would raise workflow clarity.

Suggestions

Create the referenced assets/api-dashboard.json, assets/infrastructure-dashboard.json, and assets/database-dashboard.json and move the full inline dashboard JSON into them, keeping only key excerpts in SKILL.md.

Add a short sequenced workflow (design -> define variables -> add panels -> validate JSON -> provision) with an explicit validation checkpoint before deploy.

Trim the inline panel-type and variable catalogs to one representative example each and point to a reference file for the rest to reduce token load.

DimensionReasoningScore

Conciseness

The body is mostly code examples without padded conceptual explanation, but it inlines several full dashboard JSON blobs and long catalogs (panel types, variables, alerts, provisioning, IaC) that compete for context and arguably belong in reference files rather than the overview.

3 / 5

Actionability

It provides copy-paste-ready JSON dashboards, Prometheus expressions, templating variables, alert blocks, and Terraform/Ansible provisioning covering the common cases.

5 / 5

Workflow Clarity

The content is a reference catalog with well-labeled sections but no sequenced end-to-end workflow for building/deploying a dashboard, and the Terraform/Ansible batch deploy steps lack any validation or verification checkpoint.

3 / 5

Progressive Disclosure

Sections are clearly organized and references to assets/*.json are signaled, but the referenced asset files do not exist in the bundle and large dashboard JSON that should live in those files is inlined instead.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both capability and trigger conditions with concrete language. Minor expansion of trigger synonyms would round it out.

DimensionReasoningScore

Specificity

"Create and manage production Grafana dashboards for real-time visualization of system and application metrics" lists several concrete actions (create, manage, visualize) tied to concrete targets, though it stops short of a comprehensive multi-action list.

4 / 5

Completeness

It explicitly answers both what ("Create and manage production Grafana dashboards...") and when ("Use when building monitoring dashboards, visualizing metrics, or creating operational observability interfaces") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"building monitoring dashboards, visualizing metrics, or creating operational observability interfaces" provides good natural keyword coverage, but misses common synonyms like "Grafana panels" or "metrics dashboard".

4 / 5

Distinctiveness Conflict Risk

"Grafana dashboards" carves a clear niche with distinct triggers (monitoring dashboards, observability interfaces) and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
wshobson/agents
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.