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

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A tight, Stave-specific navigation skill that respects Claude's intelligence and delivers concrete, executable guidance with a well-sequenced workflow and checkpoint. Organization is clean and appropriate for a self-contained skill with no bundle dependencies.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it jumps straight into a sequenced workflow and Stave-specific hotspots without explaining what an Electron app, IPC, or Zod is. Every line carries useful, non-obvious repo knowledge.

3 / 3

Actionability

Guidance is concrete and directly executable: specific tool calls (Agent with subagent_type 'Explore'), specific file paths to read first, and explicit dos/don'ts ("Read targeted slices with offset/limit", "Reserve manual rg/Glob chains for pinpoint lookups").

3 / 3

Workflow Clarity

The five-step Workflow is clearly sequenced, and the 'Context Already Available' section functions as an explicit validation checkpoint (check retrieved context before launching a search), with a feedback-style shortcut when the context already pinpoints the subsystem.

3 / 3

Progressive Disclosure

For a skill under 50 lines with no external bundle files needed, the content is well-organized into clearly signaled sections (Workflow, Context Already Available, Stave Hotspots, Output, Avoid) — matching the rubric's allowance for simple skills to score 3 on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

80%

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 well-formed description with explicit trigger guidance and good bilingual trigger-term coverage. It is somewhat held back by a narrow action vocabulary and modest overlap with generic code-search/overview skills.

Suggestions

Broaden the action vocabulary beyond 'explore' to concrete verbs users expect (e.g. 'locate files, map subsystem boundaries, identify entrypoints') to lift specificity.

Sharpen distinctiveness by scoping triggers to Stave-specific signals (e.g. named subsystems or 'Stave' qualifier) so it does not compete with generic code-search skills.

DimensionReasoningScore

Specificity

It names the domain ("an unfamiliar area of the Stave codebase") and a concrete action ("Explore... quickly") plus outputs (workspace structure, architecture overview, relevant files), but the action set is narrow — it lists exploration outcomes rather than multiple distinct concrete actions like extract/fill/merge.

2 / 3

Completeness

Both halves are explicit: the "what" (explore unfamiliar Stave code, surface structure/files/entrypoints) and the "when" via an explicit "Use when the request asks for..." clause listing concrete triggers.

3 / 3

Trigger Term Quality

Strong coverage of natural trigger phrasings users would actually say — "where should I look first", "관련 코드 확인", "구조 파악", and "broad code search before implementation", spanning both English and Korean variants.

3 / 3

Distinctiveness Conflict Risk

The Stave-specific framing and navigation category give it a clear niche, but "broad code search before implementation" and "architecture overview" could overlap with general code-search or planning skills, so conflict risk is reduced but not eliminated.

2 / 3

Total

10

/

12

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.