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.

1.03x

Quality

49%

Does it follow best practices?

Impact

98%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/file-organizer/SKILL.md

Quality

Content

48%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill has a genuinely well-sequenced workflow with good confirmation gates before destructive operations, but it is substantially padded with redundant example-prompt sections and generic organization advice Claude already knows. Commands are a mix of genuinely useful and non-functional (the md5 duplicate check), and nothing is split out into reference files.

Suggestions

Cut the redundant prompt-example sections ("How to Use", "Common Organization Tasks", "Related Use Cases") and the generic By Type/By Purpose/By Date taxonomies; keep one worked example and move the rest to references/examples.md.

Fix the duplicate-detection command (e.g. hash to a file then group: "find . -type f -exec md5sum {} + | sort | awk '{print $1}' | uniq -d" style, or an md5sum-based pipeline that actually groups identical hashes) and drop "[custom command]" placeholders.

Add a concrete post-execution verification step (e.g. compare file counts before/after moves, print the undo log path) to close the validation loop on the destructive batch step.

Dimension	Reasoning	Score
Conciseness	The ~430-line body includes several padded sections that teach Claude what it already knows — "By Type: Documents (PDFs, DOCX, TXT) / Images (JPG, PNG, SVG)", "By Purpose: Work vs. Personal", "By Date: Current year/month" — plus four redundant prompt-example sections ("How to Use", "Examples", "Common Organization Tasks", "Related Use Cases") and filler like "Trust the Process: Let Claude handle the cognitive load". This matches anchor 2 (noticeably verbose, several unnecessary explanations or padded sections) rather than anchor 3, where the padding would be occasional rather than recurring.	2 / 5
Actionability	There is real executable material ("du -sh [target_directory]/* \| sort -rh \| head -20", "mkdir -p", "mv"), but key commands are broken or placeholders: "find [directory] -type f -exec md5 {} \; \| sort \| uniq -d" won't actually detect duplicate files since md5 output embeds the filename in each line, and blocks like "[custom command for their setup]" and "[custom command]" are explicitly unfilled. That mix of usable commands with non-working and placeholder content fits anchor 3 (some concrete guidance but incomplete, missing key details) rather than anchor 4.	3 / 5
Workflow Clarity	The seven-step workflow (Understand Scope → Analyze → Identify Patterns → Find Duplicates → Propose Plan → Execute → Summarize) is clearly sequenced with explicit confirmation checkpoints for the destructive parts: "Always ask for confirmation before deleting", "Ready to proceed? (yes/no/modify)", and "Stop and ask if you encounter unexpected situations". It misses anchor 5 because there is no post-move verification or undo procedure — "Log all moves for potential undo" is stated as a rule but no mechanism is given — leaving minor validation gaps characteristic of anchor 4.	4 / 5
Progressive Disclosure	The body has reasonable section headers, but everything is inlined in one monolithic file with no references/, scripts/, or assets/ files; the four full worked examples, "Best Practices", and "Pro Tips" sections are exactly the content that belongs in separate reference files for a skill this size. This fits anchor 3 (some structure, but content that should be separate is inline) rather than anchor 4, which requires most content appropriately split across files.	3 / 5
	Total	12 / 20 Passed

Description

50%Weight 40%Scale 1-5

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 communicates a clear capability set (organize, find duplicates, suggest structures, automate cleanup) but omits any explicit "when to use" trigger guidance, uses second-person voice, and relies on generic keywords like "files" and "folders" rather than the natural phrases users would say. It sits at the midpoint of the rubric on nearly every dimension.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions a messy Downloads folder, finding duplicates, reorganizing folders, or cleaning up old files."

Rewrite in third person and include concrete natural trigger terms users would say: Downloads, Desktop, tidy up, declutter, duplicate files.

Trim the benefit-marketing tail ("Reduces cognitive load... without manual effort") in favor of concrete triggers that distinguish this from general file-handling skills.

Dimension	Reasoning	Score
Specificity	The description names several concrete actions — "finding duplicates, suggesting better structures, and automating cleanup tasks" — which sits at the anchor-4 level (several specific actions, minor gaps), but it is written in second person ("organizes your files", "your digital workspace"), which per the rubric guideline reduces specificity by 1. It is not anchor 2 because the domain is named with multiple real actions, not merely minimal generic ones.	3 / 5
Completeness	The "what" is clear (organize files, find duplicates, suggest structures, automate cleanup), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere — the sentence about "Reduces cognitive load and keeps your digital workspace tidy" describes a benefit, not a usage condition. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3, matching the anchor "has a clear 'what' but 'when' is missing or only weakly implied".	3 / 5
Trigger Term Quality	Phrases like "organizes your files and folders", "finding duplicates", and "cleanup tasks" give some natural keyword coverage, but common user phrasings are missing: no mention of "Downloads", "Desktop", "tidy up", "declutter", or folder names users would actually say. It fits anchor 3 (some relevant keywords, missing common variations) rather than anchor 4, which expects good coverage with only a few natural terms missing.	3 / 5
Distinctiveness Conflict Risk	Duplicate-finding and structure-suggestion give it some distinct identity, but "organizes your files and folders across your computer" is broad enough to overlap with many file-related skills (document skills, project scaffolding, backup skills). It fits anchor 3 (somewhat specific but could still overlap) rather than anchor 4, which requires a mostly distinct niche with only minor overlap.	3 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/file-organizer/SKILL.md
Commit: c9856ea

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.