CtrlK
BlogDocsLog inGet started
Tessl Logo

code-explorer

Use this skill when exploring, analyzing, or understanding project/code structure. Required for tasks like "analyze project", "explore codebase", "understand how X works".

68

Quality

83%

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

85%

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

A concise, well-structured read-only exploration skill with a clear sequenced workflow and explicit stop condition. Its main weakness is actionability: the named tools lack concrete syntax, keeping guidance from being fully executable.

Suggestions

Add concrete syntax for the referenced tools (e.g., 'grep -rn "pattern" path/' and the exact file_reader invocation) so steps are copy-paste ready.

Replace the vague 'Report clearly' with a concrete report structure (e.g., summarize findings as a short bulleted list referencing file:line).

Specify the glob pattern fully (e.g., 'glob **/* at the repo root') so the first step is unambiguous.

DimensionReasoningScore

Conciseness

Lean and efficient with short headers and imperative bullets; it never explains concepts Claude already knows and every line earns its place.

3 / 3

Actionability

Names concrete tools (glob, grep, file_reader) but without exact syntax or flags, and 'Report clearly' is vague, leaving guidance incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

A clear 5-step numbered sequence in strict order with an explicit termination checkpoint ('Stop as soon as you have enough information'); read-only exploration involves no destructive/batch ops, so the validation cap does not apply.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and organized into clear sections (Mission, Restrictions, Workflow, Rules), which satisfies the simple-skills note for a top score.

3 / 3

Total

11

/

12

Passed

Description

82%

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 with excellent natural trigger phrases and a clear what-and-when structure. It is held back by abstract action verbs and a niche broad enough to risk overlap with similar skills.

Suggestions

Replace abstract verbs with concrete actions (e.g., 'list the file tree, read the README, grep for key patterns, and summarize structure') to lift specificity.

Sharpen the niche to reduce conflict risk, e.g., 'read-only codebase exploration and summarization' to distinguish it from skills that modify code.

Add a couple more trigger variations users might say (e.g., 'map the codebase', 'where is X defined') to broaden natural-term coverage.

DimensionReasoningScore

Specificity

It names the domain and actions ('exploring, analyzing, or understanding project/code structure') but the verbs are abstract rather than a list of concrete actions, matching the 'names domain and some actions' anchor rather than the multi-action top anchor.

2 / 3

Completeness

It explicitly answers both what ('exploring, analyzing, or understanding project/code structure') and when (an explicit 'Use this skill when...' clause plus 'Required for tasks like...').

3 / 3

Trigger Term Quality

Natural trigger phrases like 'analyze project', 'explore codebase', and 'understand how X works' are exactly what a user would say, giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Code-structure analysis is a somewhat broad niche and triggers like 'analyze project' are generic enough to overlap with general code-assistant skills, so it is only somewhat specific rather than a clearly distinct niche.

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
clacky-ai/openclacky
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.