A downloads folder never gets sorted because doing it by hand is dull, and doing it with a tool feels risky: one wrong move and the thing you needed is gone.
This skill takes the risk out: nothing moves until you have seen the plan and said go, and nothing is ever deleted unless you name it yourself. That is what makes it safe to point at a folder that actually matters. The skill is below.
To get Claude to sort your files, connect the messy folder in Cowork, then run a skill that asks how you want it grouped, shows a folder plan and naming rule, and moves and renames them once you confirm, asking before each change and never deleting without permission. In plain chat it plans the tidy-up and you do the moving.
First, which setup you are on
What Claude can do depends on where you run it. Two honest cases.
To connect a folder in Cowork: open the Claude desktop app, start a Cowork session, and add the folder you want tidied, since Cowork only works on the folders you connect. Keep the app open while it runs, or the session can stall.
- From 6 October 2026, new Cowork tasks on Pro and Max run in Anthropic’s cloud, per its help page (read 4 October 2026). Your folders stay on your computer; a task fetches a copy of just the files it needs, and deleting the session deletes the copies.
- So connect only the folder you want sorted, and keep bank statements, ID scans and password files out of it.
How it works, in four stages
The skill below is these four stages. The point is that it thinks before it touches anything, and you stay in charge the whole way.
- It looks, then asks you first. Claude reads what is in the folder and, before sorting a thing, asks the questions that change the answer: group by type, by date, or by project? What should happen to the junk? Anything that must not move? You answer in a line, so the result matches how you actually think about the work.
- It shows you the plan and waits. You get a folder tree, a naming rule with worked examples, and a move map of what goes where, plus an "unsure, you decide" pile for anything that does not clearly belong. Nothing has moved yet. This is your checkpoint.
- You say go, and it does the moving. In Cowork it makes the moves and renames, confirming each change as your permission mode requires. It never deletes: if you want something gone, it asks you to confirm that file by name. In plain chat, this is where you work down the map yourself.
- It checks its own work. At the end it tells you what moved, what it left in the unsure pile and why, and the naming rule to keep using so the mess does not creep back. It confirms it deleted nothing and invented no file.
What the plan actually looks like
Say you point it at a Downloads folder holding a screenshot, two files that look like the same invoice, an installer and a notes file. After you answer its questions, stage two hands back something like this, and nothing has moved yet.
Folder tree: Documents/, Images/, Invoices/, To review/ Naming rule (with examples): 2026-08-clientname-invoice.pdf, so invoice_final_v2.pdf becomes 2026-08-acme-invoice.pdf Move map: - invoice_FINAL.pdf and invoice_final_v2.pdf look like duplicates, so both go to "To review" for you to decide. - setup.dmg is an installer, moved to "To review". - Screenshot 2026-08-14.png goes to Images. - notes.rtf goes to Documents.
You read that, change anything you want, and the plan is a draft, so you can say "actually keep invoices by client, not by date" and it re-plans, still before anything moves. When it looks right, you say go.
The file sorter skill
Download it and add it as a skill in Claude, then connect your folder and say "sort this folder". Or paste it straight into a chat with your file names underneath for the plan-only version. This is the whole method in one file.
--- name: file-sorter description: Sort and tidy a messy folder. Use when the user wants their Downloads, Desktop or a project folder organised, or says "sort my files", "tidy my downloads", "organise this folder", or "rename these properly". Acts on files in a connected folder where it can reach them, and plans the tidy-up where it cannot. --- # File sorter You are the careful hand that sorts a folder the user has been putting off opening. Nothing moves until they have seen the plan and said go, and you would rather ask twice than lose one file. You work in stages and you never reorganise anything before the user has seen the plan and said go. If you can reach the files (a connected folder), you do the moving. If you cannot, you write the plan for the user to run. You never delete a file on your own. Why the order matters: a folder that actually matters is only safe to touch if nothing moves before the user has seen it, so the look-plan-confirm order below is what keeps it safe. Privacy: work only on the folder the user connects, never the wider machine, and for the plan-only route you need the file names, not the contents of private files. ## Stage 1: Look, then ask before deciding Look at the folder, or the list of names the user gave you. Do not sort yet. Ask the questions that change the answer one at a time, waiting for each answer rather than dumping all of them at once, and offer options rather than assuming: - How should the top level be grouped: by type (documents, images, invoices), by date (year or month), by project or client, or a mix? - What should happen to the junk (installers, duplicates, obvious one-offs): move it to an "Archive" or "To review" folder, or leave it? You will not delete anything. - Are there files that must not move, or a naming pattern the user already keeps? If the folder is empty, or you cannot see the files and none were pasted, say so and stop. ## Stage 2: Propose the plan, and wait for a yes Show these, and wait for the user to confirm or change them before touching anything: - A folder tree: the new structure, matching how the user said they think about the work. - A naming rule: one pattern with two or three worked examples, for example 2026-03-clientname-invoice. - A move map: which files go where, with a short "unsure, you decide" list for anything that does not clearly belong. ## Stage 3: Do it, one safe step at a time, only after they confirm If you can reach the files, make the moves and renames, confirming each change as your permissions require. Never delete a file. If the user wants something gone, ask them to confirm it by name, one at a time. If you cannot reach the files, hand the move map over as a checklist for the user to run, worst folder first, in small batches. ## Stage 4: Check your own work When the moving is done, or the plan is ready, report back: - What moved, and what you left in the "unsure" pile and why. - The naming rule to keep using so the mess does not come back. - Confirm you deleted nothing and invented no file that was not there. - Offer to save the naming rule as a standing instruction or a note in the user's Project, so new files follow it, and offer to run this tidy again on a set day if they want it kept up.
Where the line is
- It asks before it moves, and never deletes on its own. The skill is built to show you the plan first and confirm each change. Cowork gives you three modes, Manual, Auto and Skip: keep Manual on so it asks before every move, and know that deleting a file always needs your explicit say-so. Nothing vanishes behind your back.
- A wrong move is just a move back. Nothing is deleted, so if it puts something in the wrong place you move it back, no harm done. Want a safety net the first time? Run it on a copy of the folder, or keep the move map it shows you in stage two, it is the exact list to reverse.
- It only sees the folder you connect. Claude reads the one folder you point it at, not your whole computer. For the plan-only route, paste the names, not the contents of private files, because it only needs the names to sort them.
- Read the plan before you say go. The whole safety of this is the checkpoint in stage two. Skim the tree and the map, then approve. It is your tidy-up, it just does the lifting.
If you want to go further
Comfortable in a terminal? Claude Code can do the same moving inside a folder you point it at, asking permission before each change.
If you want Claude to reach a specific folder from the desktop app without Cowork, a filesystem connector can do it, though that one means editing a small config file, so it is for the more technical. For most people, Cowork with a connected folder is the no-setup way in.
Sort your worst folder today
Do not try to fix the whole machine. Pick the one folder that makes you wince, the downloads pile or the desktop, connect just that, and run the skill. Answer its questions, read the plan, and let it clear the first stretch while you watch.
If you are on the free plan, run the same skill in a chat and act on the first ten rows of the map before you close the tab.
To stop the mess creeping back, ask it to save the naming rule as a standing instruction, then re-run the skill on the same folder once a month so the pile never builds up again. Doing this often for the same kind of work? Keep it set up so you stop re-explaining, with a Claude Project.
Questions people ask
Can I use Claude to organise my photos?
Yes, if they sit in a folder on your computer. Connect that folder in Cowork on a paid plan, and the skill asks whether to group them by type, date or project, shows you the plan, then moves and renames them once you say go.
Can Claude actually move the files on my computer?
Yes, in Cowork on a paid plan with the desktop app open and a folder connected. It reads that folder and moves and renames files in it, asking before each change, and never deletes without your say-so. In plain chat it cannot reach your disk, so it plans and you move.
Will it just start moving things without asking?
No. The skill looks first, asks how you want it grouped and what to do with the junk, then shows the plan and waits for a yes. Keep Manual mode on and it confirms each change.