CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codebase-exploration

Explore and understand codebases using SocratiCode semantic search, dependency graphs, and context artifacts. Use when exploring code, understanding architecture, finding functions/types, analysing dependencies, searching database schemas or API specs, or when socraticode/codebase_search tools are available. Activates when the user asks about code structure, wants to find where a feature lives, or needs to understand how code is organised.

Quality

87%

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

78%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 well-structured tool-dispatch skill: concrete tool names, parameters, defaults, and troubleshooting guidance organized into a clear workflow, with heavy detail correctly offloaded to a single real reference file. The main improvement opportunities are removing the thrice-stated search-before-reading rationale and adding one complete example tool invocation inline.

Suggestions

State the 'search before reading' principle once (in the intro) and cut its repetition in sections 1 and 3, including section 3's re-explanation of what a search call returns.

Add one complete example invocation (e.g. a sample codebase_search call with a query, fileFilter, and minScore) so the inline guidance is copy-paste ready without opening the reference.

DimensionReasoningScore

Conciseness

The body is largely lean and directive, but the 'search before reading / never read a file just to find out if it's relevant' rationale is repeated in the intro, section 1, and section 3, and section 3 re-explains what a search call returns. These small redundancies could be trimmed.

4 / 5

Actionability

Highly concrete for an instruction-only skill: specific tool names, parameters (fileFilter, languageFilter, minScore default 0.10), example queries ('how is authentication handled'), env-var modes, and a goal-to-tool table. No complete example invocation appears inline (deferred to the reference file), which is a minor gap.

4 / 5

Workflow Clarity

Six clearly numbered steps in a coherent order, with a dedicated troubleshooting section providing error-recovery guidance ('If search returns no results, the project may not be indexed', stale results -> codebase_update). Validation is handled as a conditional section rather than integrated checkpoints in the main flow. No destructive or batch operations, so no cap applies.

4 / 5

Progressive Disclosure

The body is a well-organized overview (workflow sections plus a goal-to-tool quick-reference table), with bulk parameter detail appropriately split into a single, clearly signaled, one-level-deep reference — references/tool-reference.md, which exists as a real file — matching the ideal structure.

5 / 5

Total

17

/

20

Passed

Description

91%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 strong description: third-person voice, concrete capabilities, and an explicit double-trigger structure ('Use when...' plus 'Activates when...') covering natural user phrasings. Its only weaknesses are minor — a few body capabilities are unmentioned and the broad 'explore codebases' framing slightly overlaps generic code-search skills.

DimensionReasoningScore

Specificity

Names several concrete actions and mechanisms — 'SocratiCode semantic search, dependency graphs, and context artifacts', 'finding functions/types, analysing dependencies, searching database schemas or API specs' — with minor gaps (e.g. circular-dependency detection and visualization from the body are not surfaced).

4 / 5

Completeness

Explicitly answers both 'what' (explore codebases via semantic search, dependency graphs, and context artifacts) and 'when' ('Use when exploring code... Activates when the user asks about code structure') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural phrasing with synonyms: 'exploring code', 'understanding architecture', 'find where a feature lives', 'how code is organised', 'asks about code structure', 'analysing dependencies', plus the explicit tool-name trigger 'socraticode/codebase_search tools are available'.

5 / 5

Distinctiveness Conflict Risk

The named tool trigger ('when socraticode/codebase_search tools are available') carves a clear niche, but 'explore and understand codebases' broadly overlaps generic code-search/grep skills, leaving minor conflict risk.

4 / 5

Total

18

/

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

giancarloerra/SocratiCode

Path

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