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.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./internal-skills/organize/SKILL.mdUse this skill when the user asks you to act on files or folders — tidy or sort a folder, move or copy files into folders, bulk or pattern rename, rename files according to what their content says, convert formats, create folder structures, archive, or move files to the trash. This is a file-organization task, not a document search: the answer is the change on disk, not information found in the files.
bash (ls, mkdir, mv, cp, and a bounded find). Read a
file (with read or bash) only when its content decides the new name or
folder, then carry the change out with bash or the file tools.rm, rmdir, unlink, find -delete,
shred, or PowerShell Remove-Item. Move what must go to the OS trash
instead (macOS /usr/bin/trash, Linux gio trash, Windows Recycle Bin).Marker-Inc-Korea/AutoRAG
399c591
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.