CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

understand-dashboard

Launch the interactive web dashboard to visualize a codebase's knowledge graph

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./understand-anything-plugin/skills/understand-dashboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced skill body built almost entirely from executable bash with explicit validation and a fallback feedback loop. The only notable weaknesses are mild redundancy in the plugin-root resolution and a large amount of inline path-hunting logic that could be split out.

DimensionReasoningScore

Conciseness

The body is almost entirely executable bash with no explanations of concepts Claude already knows, so it is broadly efficient. It stays below 5 due to trimmable redundancy: the plugin-root candidate list appears three times (prose bullets, the bash loop, and the error echo), the ": "${VAR:?}"" guards are repeated per block, and step 5 re-defaults DASHBOARD_DIR that step 3 already set.

4 / 5

Actionability

Every step is copy-paste-ready, complete bash: project/UA dir resolution, existence checks with error messages, an ordered plugin-root search loop, a pinned-viewer fast path, and fallback install/build/dev-server commands. No pseudocode or gaps for the common cases.

5 / 5

Workflow Clarity

The 8-step sequence is explicit with validation checkpoints (project directory exists, knowledge-graph.json exists, plugin root found) and a feedback loop: if the fast-path viewer exits without printing the Dashboard URL, fall back to steps 5-6. It also clearly flags which steps to skip on the fast path. Not a 4 because validation and error-recovery guidance are already explicit, not implicit.

5 / 5

Progressive Disclosure

The skill is self-contained with no bundle files, well-organized into numbered steps and a Notes section, so navigation is easy. Not 5 because at ~155 lines the multi-candidate plugin-root resolution and fallback logic (steps 3-5) are substantial inline content that could be extracted into a script/reference, and not 3 because structure and signaling are otherwise clear.

4 / 5

Total

18

/

20

Passed

Description

61%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 concise, third-person description that clearly states what the skill does with strong natural trigger terms. Its main weakness is the complete absence of a "Use when..." clause, which caps completeness and limits trigger guidance for the model.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to view, explore, or visualize the knowledge graph or codebase graph after running /understand."

Include a few natural synonyms/variations such as "graph view", "explore the codebase", or "code map" to broaden trigger coverage.

Name the tool or plugin context (e.g., "Understand Anything dashboard") to sharpen distinctiveness against other dashboard/visualization skills.

DimensionReasoningScore

Specificity

"Launch the interactive web dashboard to visualize a codebase's knowledge graph" names the domain (knowledge graph) and one concrete action (launch the dashboard), matching the 1-2 concrete actions anchor. It is not a 4 because only a single action is listed, with no coverage of related capabilities.

3 / 5

Completeness

The description clearly answers "what" (launch a web dashboard to visualize the knowledge graph) but contains no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. A score of 4 would require both what and an explicit, even if imperfect, when.

3 / 5

Trigger Term Quality

"interactive web dashboard", "knowledge graph", and "visualize" are natural phrases a user would say when wanting this skill, giving good keyword coverage. Not 5 because common variations and synonyms (e.g., "explore", "code map", "graph view", "visualization") are absent.

4 / 5

Distinctiveness Conflict Risk

The "knowledge graph" + "dashboard" framing carves out a fairly distinct niche with low overlap risk. Not 5 because the description does not name the specific tool/plugin, leaving minor conflict risk with other dashboard or visualization skills.

4 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

Egonex-AI/Understand-Anything

Path

understand-anything-plugin/skills/understand-dashboard/SKILL.md

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.