CtrlK
BlogDocsLog inGet started
Tessl Logo

the-explore-codebase

Explore an unfamiliar area of the Stave codebase quickly. Use when the request asks for workspace structure, architecture overview, relevant files, entrypoints, "where should I look first", "관련 코드 확인", "구조 파악", or broad code search before implementation.

72

Quality

88%

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

86%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, action-oriented navigation skill with concrete file paths, named tools, and retrieved-context keys; structure is clean and it avoids over-explanation. The only minor gap is one step expressed as a directive rather than a concrete instruction.

Suggestions

Convert workflow step 5 ('Read only the slices that answer the current question') into a concrete instruction, e.g. 'Use Read with offset/limit on the identified files; stop once the current question is answered.'

Add an explicit verification checkpoint before the Output section, e.g. 'Confirm the inspected files cover the requested subsystem before summarizing', to strengthen the workflow's feedback loop.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — it assumes Claude's competence, gives concrete file paths and tool calls without padding, and every line earns its place; no concept explanations Claude already knows.

5 / 5

Actionability

Provides concrete, executable guidance (specific file paths, tool names like Agent with subagent_type: 'Explore', offset/limit usage, retrieved-context keys), but workflow step 5 ('Read only the slices that answer the current question') is a directive rather than a concrete command, leaving a minor gap.

4 / 5

Workflow Clarity

Clear 5-step sequence with an implicit checkpoint ('Context Already Available' tells it to jump to targeted reads if context already pinpoints the subsystem), but there is no explicit validation/verification checkpoint; still, exploration is non-destructive so the destructive-cap does not apply.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Workflow, Context Already Available, Stave Hotspots, Output, Avoid) for a compact skill with no external bundle files, so well-structured sections alone earn the top score per the simple-skill exception.

5 / 5

Total

18

/

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, well-scoped description that clearly answers what and when, with rich natural trigger terms in two languages and a distinctive navigation niche. Voice is third person and concrete throughout.

DimensionReasoningScore

Specificity

Names the domain (exploring an unfamiliar area of the Stave codebase) plus several concrete actions implied by the trigger list (workspace structure, architecture overview, relevant files, entrypoints, broad code search), with only minor coverage gaps.

4 / 5

Completeness

Explicitly states what the skill does ('Explore an unfamiliar area of the Stave codebase quickly') and when to use it via a clear 'Use when...' clause with concrete trigger phrases, satisfying both what and when.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage in both English and Korean — 'where should I look first', 'architecture overview', '관련 코드 확인', '구조 파악', and 'broad code search' — matching phrases users would actually say.

5 / 5

Distinctiveness Conflict Risk

Scoped to a specific codebase (Stave) and a navigation/exploration niche with distinctive triggers, giving it a clear niche and minimal conflict risk with unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
sendbird/stave
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.