Semantic folder index for codebase navigation. Commands: /toondex (create), /redex (update). IMPORTANT: If you see "PROPOSE_REINDEX" in your context (injected by SessionStart hook), when the user sends their next message, briefly ask if they want you to run /redex first or if you should continue answering their question. "Oh, I see you've discovered my meticulously organized archive."
76
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
57%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 identifies a specific niche with unique command triggers, making it distinctive. However, it lacks explicit 'Use when...' guidance for Claude's skill selection, includes internal implementation details (PROPOSE_REINDEX hook) that don't aid selection, and the whimsical quote adds no functional value. The core capability could be described with more concrete actions.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms like 'navigate codebase', 'find files', 'project structure', 'folder organization'
Remove internal implementation details (PROPOSE_REINDEX hook instructions) and the decorative quote - these don't help Claude select the skill
List concrete actions the skill performs, e.g., 'Creates semantic maps of folder structures, indexes file relationships, enables quick navigation to relevant code sections'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (codebase navigation) and specific commands (/toondex, /redex), but the core capability 'semantic folder index' is somewhat abstract. Does not list concrete actions like 'indexes directories', 'maps file relationships', etc. | 2 / 3 |
Completeness | Explains what (semantic folder index, create/update commands) but lacks an explicit 'Use when...' clause. The PROPOSE_REINDEX instruction is internal behavior guidance, not user-facing trigger guidance. | 2 / 3 |
Trigger Term Quality | Includes specific command triggers (/toondex, /redex) and 'codebase navigation', but lacks natural user terms like 'find files', 'navigate code', 'folder structure', 'project map', or 'index codebase'. | 2 / 3 |
Distinctiveness Conflict Risk | The unique command names (/toondex, /redex) and specific focus on 'semantic folder index' create a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with excellent actionability and workflow clarity. The multi-step processes are clearly sequenced with validation checkpoints, and the commands are fully executable. The main weakness is verbosity in some sections, particularly the debug mode documentation which could be moved to a separate reference file to keep the main skill leaner.
Suggestions
Move the extensive Debug Mode section (approximately 100 lines) to a separate DEBUGGING.md file and reference it briefly from the main skill
Consolidate the platform detection commands into a single code block with inline comments rather than separate macOS/Linux and Windows sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose sections, particularly the extensive debug mode documentation and repeated explanations. The format specification and hook integration sections could be more concise, and some information (like platform detection details) could be trimmed. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash/PowerShell commands, concrete code examples, and copy-paste ready scripts. Each step has specific commands and clear expected outputs. | 3 / 3 |
Workflow Clarity | Clear 9-step workflow for /toondex with explicit sequencing, validation through confidence scoring, user review checkpoints for low-confidence items, and a separate well-defined /redex update flow. The 'IMMEDIATELY START WITH STEP 1' instruction ensures execution. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, references to external files (docs/INDEX_SPEC.md, references/scoring-rubric.md), and appropriate use of tables for quick reference. Content is organized logically from commands to detailed workflows to optional debug features. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (531 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
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.