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.
Overall
score
41%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:ComposioHQ/awesome-claude-skills --skill file-organizerActivation
33%The description provides a reasonable overview of file organization capabilities but suffers from marketing-style language ('Intelligently', 'Reduces cognitive load', 'tidy without manual effort') that doesn't help Claude select the skill. The complete absence of explicit trigger guidance ('Use when...') is a significant weakness that would make skill selection unreliable in a multi-skill environment.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks to organize files, find duplicates, clean up folders, or restructure their directory layout'
Replace marketing language ('Reduces cognitive load', 'without manual effort') with concrete trigger terms users would say: 'declutter', 'sort files', 'organize downloads', 'clean up desktop'
Add specific file/folder contexts to improve distinctiveness: 'Downloads folder', 'project directories', 'photo libraries', or mention specific organizational patterns
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names domain (files/folders) and some actions (finding duplicates, suggesting structures, automating cleanup), but 'understanding context' and 'intelligently organizes' are vague. Not comprehensive enough for a 3. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. The second sentence is marketing fluff ('Reduces cognitive load') rather than actionable trigger information. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'files', 'folders', 'duplicates', 'cleanup', but missing common variations users might say like 'organize my desktop', 'declutter', 'file management', 'sort files', or specific file types. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to file organization but could overlap with backup skills, file search skills, or general filesystem utilities. 'Files and folders across your computer' is broad enough to cause conflicts. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
27%This skill is significantly over-engineered and verbose, explaining basic concepts Claude already knows while burying actionable content in walls of text. The workflow has reasonable structure but lacks proper error handling and validation checkpoints for destructive operations. The entire skill could be reduced to ~50 lines with references to example files.
Suggestions
Reduce content by 80%: Remove 'When to Use', 'What This Skill Does', 'Pro Tips', and 'Best Practices' sections - Claude knows these concepts
Move examples to a separate EXAMPLES.md file and reference it with a one-line link
Add explicit validation checkpoints: 'Before any mv/rm operation, list files to be affected and require explicit confirmation'
Fix incomplete commands: Replace `[directory]` placeholders with actual variable syntax and note platform differences (macOS md5 vs Linux md5sum)
| 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 | Provides some concrete bash commands and examples, but many are incomplete or pseudocode-like (e.g., `find [directory]` with placeholders). The duplicate-finding commands are platform-specific (md5 vs md5sum) without noting this, and some commands won't work as written. | 2 / 3 |
Workflow Clarity | Has a numbered workflow (1-7 steps) with some validation ('Always ask for confirmation before deleting'), but lacks explicit feedback loops for error recovery. The 'Important Rules' section mentions stopping on unexpected situations but doesn't specify how to handle them. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including examples, pro tips, best practices, and related use cases that could be separate documents. No clear navigation structure for a 300+ line skill. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
75%Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_voice | 'description' should use third person voice; found second person: 'your ' | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 12 / 16 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.