The Daily Special

Every dish so far had you in the kitchen: you order, the agent cooks. Real kitchens have another category — the daily special. Decided once, cooked every day, no one re-orders it. In computer terms: automation. And your first one should be a chore so universally hated it needs no sales pitch: the Downloads folder.

Yours has 400 files in it. Screenshots from March. Four copies of the same PDF named (1) (2) (3). This lesson makes that someone else's job forever — and teaches the two safety rules every automation needs: move, never delete and always know the off switch.

What you'll plate today

A tidying script that organizes Downloads by file type, runs once while you watch — then gets scheduled to run every morning without you.

Ingredients

• Your first-kitchen folder
• A gloriously messy Downloads folder (you have one, don't pretend)
• About 30 minutes

Cook

1. Order the special

Write a small script that tidies my Downloads folder:

- Sort files into subfolders inside Downloads by type: images/,
  documents/, installers/, everything-else/
- SKIP anything downloaded today (I might be using it right now)
- Safety rule: MOVE files only. Never delete anything, ever.
- Write one line per moved file into tidy-log.txt in Downloads,
  with a date, so I can always see what went where.

Save it in this project, run it once now, and show me the log.

Then go look at your actual Downloads folder. Files you forgot existed, standing in labeled rows. Chore: eliminated. Now check tidy-log.txt — the log is your receipt, and receipts are what make automations trustworthy.

2. Taste and adjust the recipe

Your mess is personal, so tune it (Lesson 3 loop):

Also give screenshots their own folder, screenshots/. And anything
older than 6 months goes into archive/, keeping its type subfolder.

Run it again. Note the pleasant fact: running it twice is harmless — everything already sorted just stays put.

3. Put it on the menu — scheduling

Here's the graduation from script to automation:

Schedule this script to run every morning at 8:00 on this computer,
using the built-in scheduler (Task Scheduler on Windows / launchd
on Mac). Then:
1. Show me how to check the schedule exists
2. Show me exactly how to turn it OFF — I want to know the off
   switch before the machine does anything on its own
3. Make a save point: "downloads tidy, scheduled"

That off-switch demand isn't paranoia — it's professionalism. Never let a machine act on a schedule you don't know how to stop. Approve the permission prompts (scheduling legitimately requires them), and tomorrow at 8:00, a thing you own does work while you drink coffee.

4. Feel the shift

You now hold the automation pattern: chore → script → schedule → log → off switch. Look around your computer with new eyes. Renaming photo dumps? Backing up a folder? Weekly report skeleton? Same five steps, every time.

When it burns

• Permission prompts during scheduling — real and expected; scheduled tasks are a genuine power. Read what it asks, approve deliberately.
• A file you needed got moved — it's in a labeled subfolder, not gone (that's why rule one is move-never-delete). Check tidy-log.txt, it says exactly where.
• Downloads lives in OneDrive/iCloud — tell the agent: "my Downloads folder is inside OneDrive — find its real path first."
• Next morning: nothing ran — laptop was asleep, most likely. Ask: "change the schedule to also run at login if the 8:00 run was missed."

Order up

□ Downloads is sorted and tidy-log.txt says what moved where
□ The script survived a second run without chaos
□ It's scheduled for tomorrow morning — and you know the off switch
□ You can recite the pattern: chore → script → schedule → log → off

One honest boundary note: this was your computer and your files. Pointing this pattern at your workplace is genuinely powerful and deserves its own care — when that itch arrives, start with this recipe.

Next up — Lesson 09: New Appliances. Your agent can already cook anything in the kitchen. Next we hand it something it doesn't have yet: eyes on the internet.

Stuck on a step? Question box below.