CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

1.03x
Quality

48%

Does it follow best practices?

Impact

98%

1.03x

Average score across 3 eval scenarios

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

47%

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

The body delivers a well-sequenced, validation-checked workflow for a destructive operation, but is markedly over-long, redundant, and explains concepts Claude already knows. Actionability is decent but held back by placeholdered and slightly incorrect commands, and everything is crammed into one file with no progressive disclosure.

Suggestions

Cut redundancy: remove the 'Common Organization Tasks' section (it duplicates 'How to Use' prompts), trim full mock markdown outputs in Examples to brief sketches, and delete 'Pro Tips'/'Best Practices' filing advice Claude already knows.

Replace [target_directory]/[directory] placeholders with concrete examples and fix the duplicate-detection pipeline (e.g. use md5sum and dedup on the hash column) so commands are copy-paste ready.

Move the lengthy Examples and reference patterns into bundled reference files (e.g. examples.md) and link to them from SKILL.md to enable one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

The ~430-line body is highly verbose and redundant — 'Common Organization Tasks' repeats the 'How to Use' prompts, full mock markdown outputs pad the Examples section, and 'Pro Tips'/'Best Practices' explain filing habits Claude already knows — matching the verbose/padded anchor.

1 / 3

Actionability

It provides concrete bash commands (ls, find, du, mkdir, mv), but they use [target_directory] placeholders and the md5 duplicate-detection pipeline is not fully correct/copy-paste ready, leaving guidance incomplete.

2 / 3

Workflow Clarity

The 7-step Instructions sequence is explicit with validation checkpoints (plan approval before execution, confirm-before-delete, logging for undo, 'Stop and ask if you encounter unexpected situations'), satisfying the clear-sequence-with-explicit-validation anchor for a destructive/batch operation.

3 / 3

Progressive Disclosure

No bundle files exist and the body is a single monolithic file with clear sections but no external references; long Examples/Common Tasks/Best Practices content that should be split out is inline, fitting the some-structure-but-could-be-better-organized anchor.

2 / 3

Total

8

/

12

Passed

Description

50%

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 states concrete capabilities but omits any explicit 'when to use' trigger guidance and leans on vague benefit language ('Intelligently', 'Reduces cognitive load') in second-person voice. It is adequate but not exemplary, scoring 2 across all dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrasings, e.g. 'Use when the user asks to organize Downloads/Documents, find duplicate files, or clean up a messy folder.'

Drop vague fluff ('Intelligently', 'understanding context', 'Reduces cognitive load and keeps your digital workspace tidy without manual effort') and convert second-person 'your files' to third-person voice.

Include common user terms like 'organize', 'Downloads', 'Documents', and 'tidy up' to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

It lists several concrete actions ('finding duplicates, suggesting better structures, and automating cleanup tasks'), but the second-person 'your files and folders' / 'your digital workspace' phrasing plus the vague 'Intelligently' and 'understanding context' fluff pull it below the multi-specific-actions anchor (a 1-point voice/fluff reduction).

2 / 3

Completeness

It clearly states what the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

It includes some natural terms ('files', 'folders', 'duplicates', 'cleanup'), but misses common user phrasings ('organize', 'Downloads', 'Documents') and offers no explicit trigger clause, so coverage is only partial.

2 / 3

Distinctiveness Conflict Risk

The file-organization niche is somewhat specific, but with no distinct explicit triggers it could still overlap with generic file-management skills.

2 / 3

Total

8

/

12

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
davepoon/buildwithclaude
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.