CtrlK
BlogDocsLog inGet started
Tessl Logo

codebase-exploration

Use when exploring, understanding, or answering questions about a Repowise-indexed codebase, including architecture, where code is implemented, how a module works, or which files are relevant before reading source.

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

100%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 body is an exemplary skill document: information-dense, fully actionable with parameterized tool calls, and structured with a clear decision-flow and validation checkpoints. It assumes Claude's competence throughout and avoids bloat.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding; it never explains concepts Claude already knows and every line (tool table, flow, trust signals, error handling) earns its place.

5 / 5

Actionability

Provides concrete, parameterized tool calls (e.g. get_answer(question="…"), search_codebase(query="…", mode="auto"), get_symbol("path/to/file.py::Name")) with return-field details covering the common cases.

5 / 5

Workflow Clarity

The 'Recommended flow' is a clearly sequenced, numbered process with confidence-based decision branches and explicit 'verify when' validation checkpoints plus error-recovery guidance.

5 / 5

Progressive Disclosure

No bundle files exist and the self-contained body is well-organized into clearly signaled sections (tool table, flow, trust signals, error handling); under the simple-skill exception this warrants a 5.

5 / 5

Total

20

/

20

Passed

Description

87%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 well-crafted: it pairs an explicit 'Use when' trigger with a concrete, tool-scoped capability statement and natural user phrasing. Distinctiveness is strong thanks to the Repowise scoping. Minor specificity gains are possible by enumerating a few more discrete actions.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('exploring, understanding, or answering questions', 'architecture, where code is implemented, how a module works, or which files are relevant') with only minor gaps in coverage rather than a fully comprehensive enumeration of distinct operations.

4 / 5

Completeness

Explicitly answers both what (exploring/understanding/answering questions about a Repowise-indexed codebase) and when, with a clear 'Use when...' clause and concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('exploring', 'understanding', 'answering questions about a codebase', 'how a module works', 'which files are relevant') that users would actually say, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to a 'Repowise-indexed codebase' creates a clear niche with distinct triggers tied to a specific tool, minimizing conflict risk with other skills.

5 / 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.

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.