CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

file-organizer

6. Reduces Clutter: Identifies old files you probably don't need anymore

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/file-organizer/SKILL.md

The canonical home for this skill is file-organizer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 body is a well-structured, mostly actionable guide for file organization with a sensible approval-gated workflow, but it has a broken core duplicate-finding command, lacks post-execution verification despite performing destructive batch operations, and carries padding in the form of file-type taxonomies and template sections. Fixing the duplicate detection and adding a validation step would lift the two weakest dimensions.

Suggestions

Fix the duplicate finder so it actually locates files, e.g. `find . -type f -exec md5sum {} + | sort | awk '{print $1}' | uniq -d` followed by a hash-to-paths lookup, or just use `fdupes -r [directory]`, instead of the current hash-only pipeline.

Add an explicit post-execution validation step: compare file counts/sizes before and after the moves, print the move log for undo, and confirm nothing was lost before reporting "Organization Complete".

Trim sections that restate what Claude already knows — the By Type/By Purpose/By Date taxonomies and the boilerplate summary/maintenance templates — to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but pads with content Claude already knows: the By Type/By Purpose/By Date taxonomies (PDFs, DOCX, JPG groupings), the maintenance-tips and "Organization Complete! ✨" summary templates, and a "What This Skill Does" section that duplicates the description. It is not a 2 because there is no extensive conceptual explanation, and not a 4 because several sections could be trimmed.

3 / 5

Actionability

The analysis commands (ls, find, du, file-type counting) are executable, but the central duplicate finder `find [directory] -type f -exec md5 {} \; | sort | uniq -d` outputs only bare hashes with no filenames, making it unusable for actually locating the duplicates. Rules like "Handle filename conflicts gracefully" and "Preserve original modification dates" provide no concrete method, matching anchor 3 ("some concrete guidance but incomplete; missing key details") rather than 4's "minor gaps only".

3 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced with an approval gate ("Ready to proceed? (yes/no/modify)") and confirm-before-delete rules, but this is a destructive/batch operation and there is no post-execution verification (e.g., comparing file counts before/after or checking the undo log) and no error-recovery loop. Per the rubric's guideline, missing validation in a destructive/batch workflow caps this at anchor 3 despite the good sequencing.

3 / 5

Progressive Disclosure

No bundle files exist, and the single file is well-organized into clearly headed sections (When to Use, Instructions, Best Practices) that are easy to navigate, matching anchor 4 ("Good structure; most content is appropriately placed"). It is not a 5 because at ~254 lines it exceeds the under-50-line simple-skill exception, and the plan/summary templates and naming best practices could plausibly live in a reference file.

4 / 5

Total

13

/

20

Passed

Description

25%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 is broken: it is a single list item ("6. Reduces Clutter: ...") lifted from the body, covering only one of the skill's six capabilities, with no 'Use when...' trigger guidance and no natural trigger terms. It would rarely fire when a user asks to organize files, clean up folders, or find duplicates. It needs a full rewrite in third person covering the actual capabilities with explicit trigger conditions.

Suggestions

Rewrite the description to cover the actual capabilities in third person, e.g. "Analyzes folder structures, finds duplicate files, proposes and executes organization plans with user approval, and archives stale files" instead of the single list item.

Add an explicit trigger clause such as "Use when the user asks to organize, tidy, or clean up folders, find duplicate files, or set up a folder structure for a project."

Include natural trigger terms users actually say (organize files, clean up Downloads, tidy folders, duplicates, archive old files) so the skill fires on the right requests.

DimensionReasoningScore

Specificity

The description offers only one generic action ("Identifies old files you probably don't need anymore") and the "6." prefix is a copy-paste artifact from the body's numbered list. It names a domain loosely but omits the skill's real capabilities (duplicate finding, folder restructuring, automated moves), matching anchor 2 rather than anchor 3 which requires 1-2 concrete capability actions.

2 / 5

Completeness

There is a vague partial 'what' (one of six capabilities) and no 'when' clause or equivalent trigger guidance whatsoever, exactly matching anchor 2 ("Has a vague 'what' and no 'when'"). It cannot reach anchor 3 because the 'what' is fragmentary, not clear.

2 / 5

Trigger Term Quality

The only keywords are generic ("Reduces Clutter", "old files"); natural phrases users would say — "organize my files", "clean up my Downloads", "find duplicates", "folder structure" — are entirely absent. It is not score 1 because "old files" is a mildly relevant term, but coverage is far below anchor 3's "some relevant keywords".

2 / 5

Distinctiveness Conflict Risk

"Identifies old files you probably don't need anymore" is very broad and would collide with archiving, disk-cleanup, and download-management skills, matching anchor 2 ("Very broad; high overlap risk with many similar skills"). It is not a 1 because the clutter/old-files framing gives it slight identity beyond pure genericity.

2 / 5

Total

8

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/file-organizer/SKILL.md

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.