The most useful things you can automate with Claude Code are not impressive. They are the dull, repeated jobs that eat twenty minutes here and an hour there. Here are ten of them, each with a prompt you can adapt and the catch worth knowing before you start.
How Claude Code automation actually works
It helps to be clear about the mechanism, because it is less magical than people imagine and more reliable because of it. For most repeated jobs, Claude Code does not sit watching your computer. It writes a small program — a script — that does the job, runs it once so you can check the result, and leaves the script in your folder. From then on you can run it yourself, ask Claude Code to run it, or have your computer run it on a timetable.
That matters for two reasons. The script does the same thing every time, so a job that worked once keeps working. And you can read the script, or ask Claude Code to explain it line by line, before you trust it.
If you are new to Claude Code, the beginner's getting started guide covers installation and a safe first session. Everything below assumes you can open a folder and give an instruction.
Before you automate anything
- Test on a copy. Run every new automation on a duplicate folder first.
- Ask for a log. A script that writes down what it did is a script you can check, and undo.
- Ask for a dry run. "Show me what you would do without doing it" is a legitimate request, and a good script can support it.
The ten automations
1. A Downloads folder that sorts itself
New files land in Downloads every day and nobody files them. Ask for a script that moves them into sensible places and keeps a record:
Create a script that organises my Downloads folder: PDFs to Documents/PDFs, spreadsheets to Documents/Spreadsheets, images to Pictures in folders by year and month. Write a log of every file moved. Show me what it would do before running it.
The catch: decide what happens to duplicate names before the first run, or the script will decide for you.
2. Renaming files from what is inside them
Scanned invoices called scan0042.pdf, photos called IMG_3318.jpg. Claude Code can read each file and rename it from its contents or its date taken — "vendor_2026-08_amount.pdf" or "2026-07-14_beach.jpg".
The catch: check ten renamed files by hand before trusting the rest. Scans with poor text are where mistakes happen.
3. Pulling figures out of PDFs into a spreadsheet
For each PDF invoice in this folder, extract the date, vendor, invoice number and total, add a row to invoices.csv, and move the PDF to an Archive folder. Show me a summary when done.
This is the classic half-hour job that becomes a few seconds, and it can be re-run whenever new invoices arrive.
The catch: ask it to list any invoice it was unsure about rather than guess.
4. Cleaning up a messy spreadsheet
Duplicated rows, names in three different formats, dates as text. Describe the rules once — "one row per email address, names in Title Case, dates as YYYY-MM-DD" — and get a script you can run on next month's export too.
The catch: always write to a new file, never over the original.
5. A weekly report that writes itself
Create a script that builds weekly_report.md from my tasks.csv and the notes in the updates folder: tasks completed, tasks in progress, and a three-line summary.
Pair it with the scheduling step below and the report is waiting on Monday morning.
The catch: a report is only as tidy as its inputs. Agree a simple format for the notes first.
6. Resizing or converting a batch of images
Two hundred photos too large to email, or product images that all need to be 1200 pixels wide. Claude Code can write a script to resize, compress or convert them in one pass, into a separate output folder.
The catch: it may need to install a small image library the first time. In manual mode it will ask before installing anything.
7. Personalised documents from a template
Certificates, letters, invitations, one per row of a spreadsheet — a mail merge without the word processor. Give Claude Code a template file and a list, and ask for one finished document each.
The catch: check the first three outputs carefully; a misread column affects all of them.
8. Dated backups that tidy up after themselves
Create a backup script that copies my Documents and Projects folders into a zip file named with today's date, keeps only the last seven backups, and writes a log saying whether it succeeded.
The catch: a backup you have never restored is a hope, not a backup. Restore one file as a test.
9. Checking a website for broken links
If you run a small site, ask for a script that visits every page, follows every link, and lists any that fail. Run it monthly and dead links stop piling up.
The catch: keep it polite — one page at a time, your own site only.
10. Anything that pulls from your other tools
Connect a service through MCP and automations can reach beyond your files: summarising this week's Notion pages, collecting issues from a tracker, drafting replies from a list of contacts. Our Claude Code MCP guide explains how to connect a service safely.
The catch: anything that sends email or posts messages should stay behind a permission prompt until you have watched it work many times.
Making it run on a schedule
A script becomes true automation when it runs without you. There are two broad routes.
Your computer's own scheduler. Windows has Task Scheduler; Mac and Linux have cron and similar tools. You do not need to learn either — ask Claude Code: "Help me schedule organise_downloads to run every day at 7am. Walk me through it for my operating system." The script then runs whether or not Claude Code is open, and uses none of your Claude allowance.
Claude Code's own scheduling. The documentation describes three options for re-running a prompt rather than a script: /loop for repeating something during an open session, scheduled tasks in the desktop app that run on your machine, and cloud routines that run on Anthropic's infrastructure without your computer being on (with no access to your local files). Use these when the job genuinely needs judgement each time; use a plain script when it does not, because a script is cheaper and more predictable.
Source: Claude Code documentation — Run prompts on a schedule.
Turning a good automation into a one-word command
Once a job works, you will want to ask for it again next month without retyping the instructions. That is what Skills are for: a saved set of instructions you invoke with a slash command, such as /weekly-report. The Claude Code Skills explainer shows how to build one.
What is not worth automating
- Jobs you do once a year, unless they are painful. The setup costs more than it saves.
- Jobs that need a different judgement every time, such as negotiating by email. That is a conversation, not a script.
- Anything where a silent mistake is expensive — payments, deletions, messages to customers — without a human check in the loop.
Every example here is small on purpose. The chapter on automation in Claude Code for Beginners builds five of them in full — file organising, invoice processing, repeated emails, scheduled reports and backups — including how to test, log and schedule each one, and what to do when something goes wrong.
If you are still deciding whether this is worth paying for, count the hours: Claude Code pricing starts at the Pro plan, and one reclaimed hour a week covers it. For more starting points, see our best Claude Code prompts for beginners. And if you want a structured path from these first automations to Skills, MCP and custom agents, that is what the book is for.
Frequently asked questions
Does Claude Code run in the background all the time?
No. It works when you ask. Scheduled scripts run through your operating system's scheduler, and Claude Code's own scheduled tasks run only in the ways you configure.
Do I need to understand the scripts it writes?
Not in detail, but you should ask it to explain what a script does, in plain English, before you schedule it. That explanation is your check.
Which language are the scripts in?
Usually Python, PowerShell or a shell script, depending on your system. You can ask for a particular one.