CtrlK
BlogDocsLog inGet started
Tessl Logo

file-organizer

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

42

Quality

43%

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

61%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, actionable guide with concrete shell commands, a clear multi-step workflow, and useful naming best practices. Its main weaknesses are a missing post-execution verification step for the destructive/batch operations (capping workflow clarity) and some sections that could be tightened for token efficiency.

Suggestions

Add an explicit post-execution verification step after the 'Execute Organization' phase — e.g., re-list the new structure and confirm each moved file exists at its destination before declaring success — to satisfy the destructive/batch validation requirement.

Fix the duplicate-detection command so its output is actually usable: pipe `md5`/`md5sum` output through a hash-first format before `sort | uniq -d`, or use a dedicated hashing recipe, since raw `md5` output is not dedup-ready.

Trim the 'When to Use This Skill' bullet list and fold redundant scope questions into the Analyze step to reduce tokens without losing guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete bash commands and a compact plan template, but sections like the 'When to Use This Skill' bullet list and some explanatory lists could be tightened; it avoids heavy padding of concepts Claude already knows, placing it at 'mostly efficient but could be tightened' (3) rather than 'efficient with only minor trim opportunities' (4).

3 / 5

Actionability

It provides mostly executable guidance — real commands (ls, find, du, md5, mkdir, mv) and a concrete organization-plan template — with only minor gaps such as placeholder substitution ([target_directory]) and a slightly off duplicate-hash pipeline, matching 'mostly executable; concrete code/commands with minor gaps' (4); it is not fully copy-paste ready (5) due to those placeholders and the md5 formatting issue.

4 / 5

Workflow Clarity

The 7-step sequence (scope → analyze → patterns → duplicates → propose plan → execute → summary) is clear and includes confirmation gates ('Ready to proceed?', 'Always confirm before deleting'), but this is a destructive/batch operation with no post-execution verification loop (e.g., confirm moves landed correctly), so per the rubric's destructive-operation cap it stays at 'steps listed but validation gaps' (3) rather than 4.

3 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized section headers (When to Use, What It Does, Instructions, Best Practices) and no external references — appropriate for this task — so it fits 'good structure; most content appropriately placed; minor organization gaps' (4); it is not a 5 because no references exist and the >50-line simple-skill exception does not apply, yet the structure is genuinely good.

4 / 5

Total

14

/

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 malformed: it appears to be a numbered feature-list item ('6. Reduces Clutter:') copied into the description field rather than a purpose-written summary. It captures only one narrow capability, omits any 'Use when...' trigger guidance, and lacks the natural terms users would say when they need a file organizer.

Suggestions

Replace the description with a purpose-written third-person summary of the whole skill, e.g. 'Organizes a messy directory by analyzing structure, finding duplicates, proposing a folder layout, and moving/renaming files with approval.'

Add an explicit trigger clause: 'Use when the user's Downloads/Documents folder is cluttered, they can't find files, or they want to set up a better folder structure.'

Include natural trigger terms and concrete actions users would say — 'organize files', 'clean up Downloads', 'find duplicates', 'sort folders' — instead of the single 'identifies old files' phrasing.

DimensionReasoningScore

Specificity

The phrase 'Identifies old files you probably don't need anymore' names one concrete action, but it describes only a single sub-feature of a multi-function file organizer and never mentions the core domain (organizing, moving, restructuring folders), matching the 'names a target but actions are minimal/generic' anchor rather than the 1 (no concrete actions) or 3 (1-2 concrete actions with the domain named).

2 / 5

Completeness

It offers only a narrow, mislabeled 'what' (a numbered artifact '6. Reduces Clutter:' plus one action) and no 'when'/trigger guidance at all; per the rubric a missing 'Use when...' clause caps completeness at 3, and because the 'what' itself is vague/partial it sits at the 'vague what and no when' anchor (2) rather than a clear-what anchor (3).

2 / 5

Trigger Term Quality

It surfaces a couple of marginally natural terms ('Clutter', 'old files'), but the primary phrases a user would actually say for this skill ('organize files', 'clean up', 'sort', 'find duplicates', 'Downloads folder') are entirely absent, with no file extensions or synonyms — closer to 'one or two generic keywords missing the natural phrases' (2) than 'some relevant keywords' (3).

2 / 5

Distinctiveness Conflict Risk

'Reduces Clutter: Identifies old files you probably don't need' is very broad and would overlap with general disk-cleanup, declutter, and cleanup utilities, with no distinctive niche triggers to disambiguate it from sibling skills, matching 'very broad; high overlap risk' (2) better than 'somewhat specific' (3).

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.

Validation15 / 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
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.