CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

organize

Rules for acting on files and folders on disk — sort, move, copy, bulk-rename, rename by content, convert formats, create folder structures, or move to the trash. Plan every target path before changing anything, never overwrite or permanently delete, confirm with a listing, and report every change as old path → new path.

Quality

80%

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 ./internal-skills/organize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A tight, well-sequenced instruction skill: exact commands, platform-specific trash handling, explicit validation before and after batch changes, and a concrete reporting format. The only slack is slight redundancy with the description and a few unnamed tool references, neither of which materially hurts execution.

DimensionReasoningScore

Conciseness

The body is lean, task-specific, and assumes Claude's competence (no explanations of what bash or file systems are), but the opening paragraph restates the description's trigger list and the document-search boundary is stated twice ("not a document search" and later "Do **not** search document contents, the user's datasources, or the web"). Minor trims are possible — anchor 4, not 5.

4 / 5

Actionability

Concrete commands are named throughout (`ls`, `mkdir`, `mv`, `cp`, a bounded `find`, platform-specific `/usr/bin/trash` and `gio trash`) plus a concrete report format ("old path → new path (one per line)"), but "the converter tools", "the duplicate scan", and "the file-name discovery tools" are referenced without being named, and no concrete bulk-rename pattern is shown. Mostly executable guidance with minor gaps — anchor 4, not 5.

4 / 5

Workflow Clarity

The rules form a clear sequence with validation on both ends of a batch/destructive operation — pre-check ("check that no two targets share a name and that no target already exists before you move anything. Never overwrite an existing file") and post-check ("List the destination folder to check the changes really happened") — which clears the destructive/batch cap. Not 5: there is no explicit error-recovery loop (e.g. what to do when a target name collides beyond skipping and reporting it).

4 / 5

Progressive Disclosure

The body is 35 lines, needs no external references (none exist in the bundle, and none are referenced), and is organized into clearly labeled sections ("How to do it", "Rules") with bolded rule names — matching the simple-skill exception where a short, well-organized skill with no external references scores 5.

5 / 5

Total

17

/

20

Passed

Description

71%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.

A highly specific, action-dense description with concrete safety behaviors, but it omits any explicit "Use when..." trigger clause, which caps completeness, and it misses the natural synonyms (organize, tidy up, clean up) users would most often say for this task. Distinctiveness is good, with only minor overlap risk from the generic "convert formats" phrasing.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to organize, tidy, sort, bulk-rename, or clean up files and folders" — this directly answers 'when' and lifts completeness past the cap.

Include the natural synonyms users actually say — "organize", "tidy up", "clean up", "archive" — alongside the current action verbs to broaden trigger-term coverage.

Tie "convert formats" to file format conversion (e.g. "convert file formats") to reduce overlap with document-processing and format-conversion skills.

DimensionReasoningScore

Specificity

The description lists eight concrete actions ("sort, move, copy, bulk-rename, rename by content, convert formats, create folder structures, or move to the trash") plus concrete behaviors ("Plan every target path before changing anything, never overwrite or permanently delete, confirm with a listing, and report every change as old path → new path"), matching the comprehensive-coverage anchor. Not 4: the action list has no notable coverage gaps.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description; the 'when' is only weakly implied by "acting on files and folders on disk". Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3. Not 4: the 'when' is not merely imprecise, it is absent.

3 / 5

Trigger Term Quality

Natural action verbs users would say are present ("sort", "move", "copy", "bulk-rename", "trash"), but common phrasings like "organize", "tidy up", or "clean up" are absent. This is good coverage with a few natural terms missing (anchor 4), not comprehensive synonym coverage (anchor 5).

4 / 5

Distinctiveness Conflict Risk

The action list ("bulk-rename", "move to the trash", "create folder structures") carves a clear file-management niche with distinct triggers, but generic phrases like "convert formats" and "move" carry minor overlap with format-conversion and document-handling skills — mostly distinct with minor overlap risk (anchor 4), not a fully conflict-free niche (anchor 5).

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Marker-Inc-Korea/AutoRAG

Path

internal-skills/organize/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.