Fast codebase navigator - finds files and code patterns quickly
68
Quality
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/explorer/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description provides a basic understanding of the skill's purpose but is too terse to be effective for skill selection. It lacks explicit trigger guidance, comprehensive action details, and natural user keywords. The 'quickly' qualifier is vague marketing language that doesn't add functional value.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when searching for files, locating functions, finding code patterns, or navigating unfamiliar codebases'
Include natural trigger terms users would say: 'search', 'find', 'locate', 'grep', 'where is', 'look for', specific file types
Expand specific capabilities: what search methods are supported (regex, fuzzy, semantic), what can be found (functions, classes, imports, references)
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (codebase navigation) and mentions two actions (finds files, finds code patterns), but lacks comprehensive detail about specific capabilities like search methods, file types, or what 'quickly' means in practice. | 2 / 3 |
Completeness | Describes what it does (finds files and code patterns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords ('codebase', 'files', 'code patterns') but misses common variations users might say like 'search', 'grep', 'find function', 'locate', 'where is', or specific file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to code navigation but could overlap with general code search tools, IDE features, or file management skills. The term 'codebase navigator' provides some distinction but 'finds files' is quite generic. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that provides concrete, executable search commands without unnecessary explanation. The main weakness is the lack of workflow guidance for combining search strategies or handling complex multi-step searches. The response format section, while useful, adds bulk that could be externalized.
Suggestions
Add a brief workflow example showing how to combine tools (e.g., 'Find definition, then find all usages' as a 2-step process)
Consider moving the detailed response format to a separate RESPONSE_FORMAT.md file and referencing it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only essential commands and patterns without explaining what grep, fd, or ripgrep are. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable bash commands with real-world examples. Commands are copy-paste ready with clear flags and patterns demonstrated. | 3 / 3 |
Workflow Clarity | While individual search commands are clear, there's no sequenced workflow for complex searches or guidance on combining tools. The 'When to Use Explorer' section lists use cases but doesn't provide step-by-step processes for achieving them. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. For a skill of this size (~60 lines), this is acceptable, but the response format example is lengthy and could be referenced separately. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
fab464f
Table of Contents
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.