redex
Update existing index.toon with changes. Detects new/deleted/modified folders and updates the semantic folder index.
56
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
17%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 function but suffers from technical jargon that users wouldn't naturally use and completely lacks trigger guidance. The absence of a 'Use when...' clause makes it difficult for Claude to know when to select this skill from a larger pool.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to refresh the folder index, sync directory changes, or update the project structure after adding/removing folders'
Replace or supplement technical terms like 'index.toon' with natural language users would say, such as 'folder index', 'directory structure', or 'project organization'
Expand the capability list to include more specific actions like 'tracks folder additions, removals, and renames' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (index.toon, semantic folder index) and some actions (detects new/deleted/modified folders, updates), but doesn't comprehensively list all concrete actions or capabilities. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Uses technical jargon ('index.toon', 'semantic folder index') that users would not naturally say. Missing common terms users might use like 'update index', 'refresh folders', or 'sync directory'. | 1 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'index.toon' provides some distinctiveness, but 'semantic folder index' is vague enough to potentially overlap with other indexing or folder management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides actionable, executable guidance with clear git commands and a well-defined workflow for updating index files. The main weaknesses are verbosity from repeated execution imperatives and missing error handling/validation steps for edge cases like git failures or corrupted index files.
Suggestions
Remove redundant 'DO THIS NOW' and 'EXECUTE IMMEDIATELY' phrases - a single clear instruction at the top is sufficient
Add error handling guidance for when git commands fail or when index.toon is malformed
Consolidate the 'When to Use' and 'What It Does' sections into the main workflow or remove them entirely since Claude can infer this context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has significant redundancy with multiple 'DO THIS NOW' and 'EXECUTE IMMEDIATELY' instructions repeated throughout. The 'When to Use' and 'What It Does' sections explain things Claude could infer. However, the core technical content is reasonably efficient. | 2 / 3 |
Actionability | Provides concrete, executable git commands, specific output formats, and clear examples of the diff presentation. The step-by-step process includes actual bash commands and specific file patterns to follow. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-5) with a user approval checkpoint before applying changes. However, there's no explicit validation or error recovery for git command failures, missing index.toon scenarios mid-process, or handling of merge conflicts in the index. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate cross-references to related skills (/toondex), and a 'See Also' section. Content is appropriately scoped for a single skill file with references to the main documentation for deeper details. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.