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.

54

1.03x
Quality

30%

Does it follow best practices?

Impact

98%

1.03x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/file-organizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

32%

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 the general domain of file and folder organization with some specific capabilities like duplicate detection and structure suggestions, but relies on marketing-style language ('intelligently', 'reduces cognitive load', 'without manual effort') rather than concrete technical actions. It critically lacks a 'Use when...' clause, making it harder for Claude to know when to select this skill, and uses second person ('your files', 'your computer') which reduces professionalism.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks to organize files, find duplicate files, clean up directories, restructure folders, or declutter their filesystem.'

Replace vague/marketing language ('intelligently', 'reduces cognitive load', 'without manual effort') with concrete actions like 'renames files using consistent naming conventions, moves files into categorized subdirectories, identifies and removes duplicate files by content hash.'

Switch from second person ('your files', 'your computer') to third person voice (e.g., 'Organizes files and folders by analyzing directory structures, detecting duplicates, and suggesting improved hierarchies.').

DimensionReasoningScore

Specificity

Names the domain (files and folders) and lists some actions (finding duplicates, suggesting better structures, automating cleanup tasks), but uses vague language like 'understanding context' and 'intelligently organizes' which are more buzzwords than concrete actions. Missing specifics like file types, rename patterns, or directory restructuring commands.

2 / 3

Completeness

Describes what it does (organizes files, finds duplicates, suggests structures, automates cleanup) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'when' is not even implied clearly, so this scores at the lower end.

1 / 3

Trigger Term Quality

Includes some relevant terms like 'files', 'folders', 'duplicates', 'cleanup', and 'organize', but misses common user phrases like 'sort files', 'declutter', 'rename', 'move files', 'directory structure', 'file management', or specific file extensions. The phrase 'digital workspace' is somewhat natural but vague.

2 / 3

Distinctiveness Conflict Risk

The focus on file/folder organization and duplicate detection gives it some distinctiveness, but the broad scope ('across your computer') and vague terms like 'automating cleanup tasks' could overlap with general file management, backup, or system maintenance skills.

2 / 3

Total

7

/

12

Passed

Implementation

27%

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

This skill is far too verbose for what it accomplishes, spending many tokens on concepts Claude already understands (file types, basic shell commands, what organization means) and repeating itself across sections. While the 7-step workflow provides reasonable structure with an approval gate, the lack of concrete validation/undo mechanisms and some non-functional command examples weaken its actionability. The entire document should be dramatically condensed with advanced examples and best practices split into separate files.

Suggestions

Cut the content by at least 50%: remove 'When to Use', 'What This Skill Does', 'Pro Tips', 'Best Practices', 'Related Use Cases', and 'Common Organization Tasks' sections entirely — Claude doesn't need motivation or use-case lists.

Fix the duplicate-finding commands to be actually executable (the md5 pipeline shown won't work) and note platform differences (macOS md5 vs Linux md5sum, GNU find -printf).

Add a concrete undo/logging mechanism — show actual code for logging moves to a file that can be reversed, since the skill involves destructive file operations.

Split examples and reference material into separate files (e.g., EXAMPLES.md, PATTERNS.md) and reference them from a much leaner SKILL.md overview.

DimensionReasoningScore

Conciseness

Extremely verbose at ~300+ lines. Explains obvious concepts Claude already knows (what file types are, what duplicates are, basic bash commands like mkdir and mv). The 'When to Use This Skill' section, 'What This Skill Does' summary, 'Pro Tips', 'Best Practices', and 'Related Use Cases' sections are largely unnecessary padding. The 'Common Organization Tasks' section just repeats example prompts. Much of this could be cut by 60-70%.

1 / 3

Actionability

Provides some concrete bash commands (find, du, md5) and shows executable examples, but many commands have placeholder syntax like `[target_directory]` and some are platform-specific without noting it (e.g., `md5` vs `md5sum`, `-printf` is GNU-specific). The photo organization example mentions EXIF data extraction but provides no actual code for it. The duplicate-finding commands are incomplete (the md5 pipeline wouldn't actually work as shown for finding duplicates).

2 / 3

Workflow Clarity

The 7-step workflow is clearly sequenced and includes an approval checkpoint before executing changes ('Ready to proceed?') and mentions confirming before deleting. However, there's no explicit undo/rollback mechanism despite mentioning 'log all moves for potential undo' — no actual logging implementation is shown. Missing a concrete validation step after organization is complete (e.g., verify file counts match, no files lost).

2 / 3

Progressive Disclosure

This is a monolithic wall of text with no references to external files. Everything is inline — the examples, best practices, common tasks, and pro tips could all be split into separate reference files. The skill tries to be comprehensive in a single document, resulting in an overwhelming amount of content that would consume significant context window space.

1 / 3

Total

6

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
Lingjie-chen/MT5
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.