CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

explore-codebase

Navigate and understand codebase structure using the knowledge graph

Quality

78%

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/explore-codebase/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 tight, actionable playbook with exact tool names, parameters, and an explicit call-ordering rule, well-organized and free of padding.

DimensionReasoningScore

Conciseness

The body is lean and operational — it lists specific tool calls and rules with zero concept explanation or padding, assuming Claude's competence; every token earns its place.

5 / 5

Actionability

It names exact tools with concrete arguments (e.g. query_graph_tool with callers_of/callees_of/imports_of, detail_level="minimal"), giving fully executable guidance that covers the common navigation cases.

5 / 5

Workflow Clarity

A clear numbered six-step sequence with an explicit ordering constraint ('Call get_minimal_context_tool before any other graph tool'), but it lacks explicit validation checkpoints; since the skill is read-only the destructive-batch cap does not apply.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed; content is well-organized into clear sections (Explore Codebase, Steps, Token Efficiency Rules), qualifying for the simple-skill exception of 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 is concise, third-person, and names a clear domain and actions, but it lacks any 'Use when...' trigger guidance, which limits its completeness and trigger discoverability.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when navigating or exploring a codebase, finding functions/classes, or tracing call relationships').

Swap the jargon 'knowledge graph' for more natural user-facing terms like 'codebase map' or 'code relationships' alongside the technical term.

Expand the action list beyond 'navigate and understand' to concrete operations like 'find functions, trace callers and callees, follow execution flows'.

DimensionReasoningScore

Specificity

Names the domain ('codebase structure') plus two actions ('Navigate and understand'), but those actions are somewhat abstract and coverage is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

It states a clear 'what' (navigate/understand codebase structure) but provides no 'when'/'Use when' clause, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

'codebase' is a natural user term, but 'knowledge graph' is technical jargon users rarely say and common variations like 'explore' or 'find' are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'knowledge graph' qualifier carves a distinct niche with minimal conflict risk, though 'navigate codebase' could overlap with general explore/search skills, fitting the 'mostly distinct; minor overlap' anchor.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tirth8205/code-review-graph

Path

skills/explore-codebase/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.