CtrlK
BlogDocsLog inGet started
Tessl Logo

dashboard-builder

Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms. Use when turning metrics into a working dashboard instead of a vanity board.

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dashboard-builder/SKILL.md

The canonical home for this skill is tdg-personal/dashboard-builder

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is concise, well-structured, and self-contained with a clear workflow and concrete per-platform panel guidance. Its main gaps are the absence of executable examples (JSON skeleton, query snippets) and an explicit validation feedback loop in the workflow.

Suggestions

Add a minimal example dashboard JSON skeleton or a sample query (e.g., a PromQL/LogQL snippet) to make the guidance copy-paste ready and lift actionability.

Insert an explicit validation step in the workflow (e.g., load/preview the generated JSON and fix before finalizing) to add a validate->fix->retry checkpoint.

Provide concrete default threshold/status-color guidance for at least one example panel set, since the checklist requires meaningful thresholds but none are shown.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven with no padding or explanation of concepts Claude already knows (Grafana, Kafka, JVM heap, p99); every line earns its place.

3 / 3

Actionability

Gives concrete process guidance (named panel categories, ordered board structure, per-platform panel sets) but provides no executable artifacts such as example dashboard JSON, query snippets, or threshold values.

2 / 3

Workflow Clarity

A clear four-step numbered sequence exists with a quality checklist, but there is no explicit validation feedback loop (e.g., load JSON, fix, reload) embedded in the workflow.

2 / 3

Progressive Disclosure

Self-contained, well-organized into clear sections with no nested or broken references; no bundle files exist, so the simple-skill carve-out applies.

3 / 3

Total

10

/

12

Passed

Description

75%

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

The description is concise and explicit, covering what the skill does and when to use it with a clear 'Use when' trigger. It carves a distinct niche via named platforms, though its action list is somewhat narrow and common trigger-term variations are not all covered.

DimensionReasoningScore

Specificity

Names the domain ('monitoring dashboards') and a concrete action ('Build monitoring dashboards', 'turning metrics into a working dashboard'), but does not enumerate multiple distinct concrete actions as a score-3 example would.

2 / 3

Completeness

Clearly states what it does ('Build monitoring dashboards that answer real operator questions') and an explicit 'Use when...' trigger clause, satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural platform names a user would say ('Grafana, SigNoz') and 'monitoring dashboards', but misses common variations like 'observability dashboard' or 'metrics dashboard', and 'vanity board' is internal jargon.

2 / 3

Distinctiveness Conflict Risk

Named platforms and the 'operator questions' / 'working dashboard instead of a vanity board' framing carve a clear observability-dashboard niche unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.