CtrlK
BlogDocsLog inGet started
Tessl Logo

exploring-codebase

Systematic codebase exploration that maps architecture, components, and dependencies. Use when you need to understand how a feature works across a codebase, explore an unfamiliar project's architecture, trace data flow through multiple layers, or plan changes that span several components. Maps the high-level structure first, then dispatches parallel agents to explore each area in depth. Produces a synthesis with file:line references, execution flows, and actionable recommendations.

87

1.63x
Quality

81%

Does it follow best practices?

Impact

90%

1.63x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Discovery

85%

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

This is a strong skill description that clearly articulates both capabilities and usage triggers. It excels at specificity by describing the methodology (parallel agents, synthesis with references) and provides explicit 'Use when' guidance. The main weakness is trigger term coverage could include more natural user phrasings.

Suggestions

Add natural trigger terms users might say, such as 'code structure', 'how does this work', 'navigate codebase', or 'find implementation'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'maps architecture, components, and dependencies', 'maps high-level structure', 'dispatches parallel agents', 'produces synthesis with file:line references, execution flows, and actionable recommendations'.

3 / 3

Completeness

Clearly answers both what (systematic codebase exploration, mapping architecture, parallel agent dispatch, synthesis production) AND when with explicit 'Use when' clause covering multiple trigger scenarios (understand features, explore unfamiliar projects, trace data flow, plan changes).

3 / 3

Trigger Term Quality

Contains relevant terms like 'codebase', 'architecture', 'data flow', 'components', 'dependencies', but missing common variations users might say like 'code structure', 'how does X work', 'navigate code', or 'find where'.

2 / 3

Distinctiveness Conflict Risk

Clear niche focused on systematic multi-component codebase exploration with specific methodology (parallel agents, file:line references). Distinct from general code editing or single-file analysis skills.

3 / 3

Total

11

/

12

Passed

Implementation

77%

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

This is a well-structured skill with excellent workflow clarity and actionability. The three-phase approach with validation gates is exemplary for complex multi-step operations. Minor weaknesses include some redundancy between sections (Do/Don't vs inline guidance) and the file length could benefit from splitting detailed examples into separate references.

Suggestions

Remove redundant guidance that appears in both prose and the Do/Don't table to improve conciseness

Consider moving the 'Adaptive Examples' section to a separate EXAMPLES.md file and linking to it

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some redundant explanations (e.g., the 'Core rule' paragraph restates what the table already shows). The Do/Don't table partially duplicates guidance from earlier sections.

2 / 3

Actionability

Provides concrete, copy-paste ready Task dispatch blocks with specific parameters, clear agent file references, and explicit model choices. The validation checklists and state tracking block are immediately usable.

3 / 3

Workflow Clarity

Excellent multi-phase workflow with explicit validation gates between each phase. Clear feedback loops (re-prompt if incomplete), numbered steps, and explicit exit criteria ensure Claude knows exactly when to proceed or retry.

3 / 3

Progressive Disclosure

References external files appropriately (agents/discovery-agent.md, templates/synthesis-output.md) but the main skill file is quite long. Some content like the adaptive examples and integration section could potentially be split out, though the references that exist are well-signaled.

2 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
emptyaltoidstin/ntm-orchestrator
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.