CtrlK
BlogDocsLog inGet started
Tessl Logo

understand-chat

Use when you need to ask questions about a codebase or understand code using a knowledge graph

76

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, actionable reference: it gives executable shell commands, a clear sequenced workflow with a freshness validation checkpoint, and well-organized sections without unnecessary concept explanation. It reads as token-efficient and copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and structured — it assumes Claude's competence with git/grep, avoids explaining basic concepts, and every section (graph structure reference, efficient reading, instructions) earns its place; it is not padded with concepts Claude already knows.

3 / 3

Actionability

It provides concrete, copy-paste-ready commands (the UA_DIR resolver, the git rev-parse/diff block, grep patterns against the graph JSON), matching the 'fully executable code/commands' anchor rather than vague or pseudocode guidance.

3 / 3

Workflow Clarity

Steps 1-7 are explicitly sequenced with a validation checkpoint (graph-freshness check in step 2) and feedback guidance ('If not, tell the user to run /understand first', warn before answering), satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files are needed; the single SKILL.md is organized into well-labeled sections (Graph Structure Reference, How to Read Efficiently, Instructions), which per the simple-skills scoring note qualifies for a top score without external file references.

3 / 3

Total

12

/

12

Passed

Description

90%

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, uses third person, and supplies an explicit 'Use when' trigger covering both what and when. It is strong overall, with the only soft spot being capability specificity — it states the general purpose rather than enumerating several concrete actions.

DimensionReasoningScore

Specificity

It names the domain ("codebase", "knowledge graph") and two actions ("ask questions", "understand code") but does not list multiple distinct concrete capabilities, matching the 'names domain and some actions, but not comprehensive' anchor rather than the 'lists multiple specific concrete actions' level above.

2 / 3

Completeness

The explicit "Use when you need to ask questions about a codebase or understand code using a knowledge graph" clause answers both what (understand/ask about code via a knowledge graph) and when, with an explicit trigger.

3 / 3

Trigger Term Quality

Natural phrasings a user would say ("ask questions about a codebase", "understand code") are present alongside the tool-specific "knowledge graph", giving good coverage of natural trigger terms; it is not merely generic jargon.

3 / 3

Distinctiveness Conflict Risk

The knowledge-graph niche and codebase-questioning trigger are a clear, distinct scope unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
Egonex-AI/Understand-Anything
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.