file-organizer
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
54
Quality
30%
Does it follow best practices?
Impact
98%
1.03xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/file-organizer/SKILL.mdDiscovery
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.
The description provides a reasonable overview of file organization capabilities but suffers from missing explicit trigger guidance ('Use when...'), which is critical for skill selection. The language leans toward marketing fluff ('Reduces cognitive load', 'without manual effort') rather than concrete, actionable descriptions that help Claude choose this skill appropriately.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks to organize files, clean up folders, find duplicate files, or restructure their directory layout'
Replace vague phrases like 'understanding context' and 'reduces cognitive load' with specific actions like 'categorize files by type', 'identify and remove duplicate files', 'create folder hierarchies based on file metadata'
Include natural user terms like 'declutter', 'sort my downloads', 'organize my desktop', 'file management', or common folder names like 'Downloads', 'Documents'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (files/folders) and lists some actions ('finding duplicates, suggesting better structures, automating cleanup tasks'), but these are somewhat vague and not fully concrete actions like 'move files to X' or 'rename based on Y'. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. The rubric states missing explicit trigger guidance should cap completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms ('files', 'folders', 'duplicates', 'cleanup') but misses common user phrases like 'organize my desktop', 'sort downloads', 'declutter', 'file management', or specific folder names users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to file organization but could overlap with backup skills, file search skills, or general filesystem utilities. Terms like 'digital workspace' and 'cognitive load' are vague and don't create clear boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is significantly over-engineered with excessive verbosity that explains obvious concepts to Claude. While it contains some useful bash commands and a reasonable workflow structure, the content could be reduced by 70%+ without losing actionable value. The lack of progressive disclosure and explicit validation checkpoints for destructive file operations are notable weaknesses.
Suggestions
Reduce content to ~50-75 lines by removing explanations of what file types are, obvious tips, and the 'When to Use' section - Claude knows when file organization is needed
Extract examples, best practices, and pro tips into separate reference files (EXAMPLES.md, BEST_PRACTICES.md) with clear links from the main skill
Add explicit validation steps after file moves: verify destination exists, check file count matches, provide rollback command if issues detected
Replace placeholder commands like `find [directory]` with concrete, copy-paste ready examples using common paths like `~/Downloads`
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 300+ lines with extensive explanations Claude doesn't need (what file types are, basic bash commands, obvious tips like 'use clear, descriptive names'). The 'When to Use This Skill' and 'What This Skill Does' sections explain concepts Claude already understands. | 1 / 3 |
Actionability | Contains some concrete bash commands and examples, but many are incomplete or pseudocode-like (e.g., `find [directory]` with placeholders). The duplicate-finding commands are useful but the overall guidance mixes actionable code with vague instructions like 'organize systematically'. | 2 / 3 |
Workflow Clarity | Has numbered steps and mentions asking for confirmation before deleting, but validation checkpoints are implicit rather than explicit. Missing clear feedback loops for error recovery when file operations fail. The 'Execute Organization' section lacks verification steps after moves. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including examples, best practices, and pro tips that could be separate reference documents. No clear navigation structure for a 300+ line skill file. | 1 / 3 |
Total | 6 / 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 | |
- 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.