CtrlK
BlogDocsLog inGet started
Tessl Logo

dashboard

Use when reading, editing, or creating files in dlt/_workspace/helpers/dashboard/ or tests/workspace/helpers/dashboard/ or tests/e2e/

61

Quality

71%

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 ./.claude/skills/dashboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The content is a high-quality, concise orientation guide with strong actionability through concrete paths, a routing table, and named test fixtures. Its main weakness is that it is entirely monolithic with no progressive disclosure into separate reference files.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanations of concepts Claude already knows; every section (file layout, architecture, routing table, conventions) earns its place and respects the token budget.

5 / 5

Actionability

Provides concrete, executable guidance including exact file paths, a "Where to Put New Code" routing table, specific test commands, and named fixtures — the only minor gap is the absence of an example code snippet for a cell.

4 / 5

Workflow Clarity

Sequences are clear where applicable (test-running commands, where-to-add-tests guidance) and the navigation structure is unambiguous; as an orientation/reference skill it has no destructive steps requiring validation, so it approaches but does not quite reach the explicit-checkpoint bar of 5.

4 / 5

Progressive Disclosure

Content is well-structured with clear section headers and a navigable routing table, but it is monolithic — all detail lives inline in SKILL.md with no one-level-deep reference files splitting out the larger material.

4 / 5

Total

17

/

20

Passed

Description

60%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.

The description has a strong, explicit "Use when" trigger with highly distinctive path-based scoping, but it lacks a clear statement of what the skill does and relies on path jargon rather than natural user language. Strengthening the "what" and adding natural trigger terms would raise it.

Suggestions

Add a brief "what" clause stating what the skill provides, e.g. "...provides the dashboard's file layout, module responsibilities, and conventions for where new code belongs. Use when..."

Include natural-language trigger terms users would say (e.g. "dashboard", "marimo app", "pipeline inspector UI") alongside the path triggers.

Replace generic verbs ("reading, editing, or creating files") with more specific capability language that reflects the development-guide purpose.

DimensionReasoningScore

Specificity

Lists three concrete actions ("reading, editing, or creating files") tied to specific directory paths, placing it above the 3-anchor with several specific actions but with minor gaps since the verbs are generic and the description never says what the skill produces.

4 / 5

Completeness

An explicit "Use when" clause is present and strong, but the "what" is only weakly implied by the generic action verbs — it never states what the skill actually does or provides, so it does not reach the both-what-and-when bar of 4.

3 / 5

Trigger Term Quality

Triggers are concrete path-based strings ("dlt/_workspace/helpers/dashboard/", "tests/e2e/") which are useful for routing but are technical jargon rather than natural phrases a user would say, missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

The highly specific dashboard and test directory paths create a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

15

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dlt-hub/dlt
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.