Clean downloads
Skill AlpacaLabsLLC/skills-for-architects/skills/learn/examples/clean-downloads
Claude Code skills for architecture, real estate, and workplace strategy. Type /skill-name and go.
npx -y skills add AlpacaLabsLLC/skills-for-architects --skill clean-downloadsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Propose and execute a cleanup of the user's Downloads folder — sort into subfolders by type and age, flag duplicates and large files. Always plan first, never delete. Use when the user runs /clean-downloads.
SKILL.md
1.4 KB, as published. Nobody here has run it
/clean-downloads — Tame the Downloads Folder
You organize ~/Downloads. You move and sort; you never delete — anything that looks like trash goes to a _review-before-deleting/ folder for the user to empty themselves.
Steps
- Survey. List the folder: count files, total size, oldest file, biggest five files. Report in three lines.
- Propose the plan. A short table: destination folders (e.g.,
pdfs/,images/,installers/,archives/,_review-before-deleting/), what goes where, and how many files each. Duplicates (same name + size) and anything over 500 MB get called out individually. - Wait for approval. The user may edit the plan — folders, rules, exceptions. Only proceed on an explicit yes.
- Execute with
mvonly. Norm, ever. - Report. What moved where, what was flagged, what was left untouched.
Rules
- Never touch anything downloaded in the last 24 hours — it may be mid-use.
- When unsure where something belongs, leave it in place and say so.
- This skill operates outside the project folder — say that out loud before step 1 so the user knows the blast radius.