CtrlK
BlogDocsLog inGet started
Tessl Logo

codebase-exploration

Use when exploring, understanding, or answering questions about a codebase that has Repowise indexed (a .repowise/ directory in the project root). Activates for "how does X work", "explain the architecture", "where is Y implemented", "what does this module do", or any task that needs an understanding of structure before diving into source files.

76

Quality

93%

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

92%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 tight, well-structured instruction skill: every section is actionable, the recommended flow is explicitly sequenced with trust-signal validation checkpoints, and there is no padding or over-explanation. It exemplifies token-efficient, navigation-friendly SKILL.md content.

DimensionReasoningScore

Conciseness

Lean throughout: it assumes Claude's competence, never explains what an index or a wiki is, and every line (tool table, flow, trust signals) earns its place. The dense table cells pack multiple tools' routing rules without padding.

5 / 5

Actionability

Provides concrete, callable tool signatures (get_answer(question="…"), search_codebase(mode="auto"), get_symbol("path::Name")) with specific argument guidance. Slightly short of fully copy-paste-ready since exact argument values are left to the user's question.

4 / 5

Workflow Clarity

The "Recommended flow" gives a numbered, sequenced procedure with explicit decision branches (high vs medium/low confidence routing to best_guesses/fallback_targets) and a dedicated "Trust signals — verify when" section that functions as validation checkpoints with feedback into get_context/get_symbol.

5 / 5

Progressive Disclosure

Well-organized overview with clear section headers and no nested references; no bundle files exist so all content is appropriately self-contained and easy to navigate at one level.

5 / 5

Total

19

/

20

Passed

Description

95%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, concrete description that explicitly covers what and when with natural trigger phrases and a distinguishing precondition (.repowise/). It is distinct from generic code-exploration skills and would reliably activate for the right tasks.

DimensionReasoningScore

Specificity

Lists several concrete actions ("exploring, understanding, or answering questions about a codebase") and ties them to specific tool calls, though coverage is oriented around a single indexed-codebase scenario rather than many distinct actions.

4 / 5

Completeness

Explicitly answers both what (exploring/understanding/answering questions about an indexed codebase via Repowise MCP tools) and when (the "Activates for" clause with concrete trigger phrases and the .repowise/ precondition).

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say ("how does X work", "explain the architecture", "where is Y implemented", "what does this module do") plus the concrete Repowise/indexed-repo signal.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Repowise-indexed repos with a .repowise/ directory) with distinct triggers, making conflict with unrelated exploration skills unlikely.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
repowise-dev/repowise
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.