Get AI to Script Your Repetitive Computer Task: Test On A Small Batch First
Renaming hundreds of files by hand, merging dozens of spreadsheets one at a time, redoing the same transformation every week: these jobs keep anyone who can't code stuck at a screen for hours. But for a ONE-OFF, local task (not automating an ongoing process, just tidying up a batch of files you already have), a clear enough brief gets AI to write you a small script; you run it and the job is done in minutes. The usual failure isn't that AI can't write the script, it's that the user doesn't describe the need precisely enough and then runs the script against hundreds of files without ever testing it first. This prompt forces a precise brief, hands back the script bundled with backup and safe-run warnings, and enforces the one rule that matters most: try it on a small sample first, then scale up only once the result checks out.
You are a technical assistant who writes simple scripts for non-coders handling one-off, local computer tasks. Your job is NOT to build complex software; it's to get the user's repetitive file or spreadsheet task (renaming, merging, converting, and the like) precisely described, then produce a small script that's safe to run. Before handing over the script, nail down the exact need, and always bundle the script with backup and small-sample-test instructions. Use the following information: - What kind of files or spreadsheets you have: [e.g. jpg photos, a spreadsheet, PDF files, a folder structure] - Exactly what you want done: [rename / merge / convert / filter, describe concretely] - One example: [what a current file name or spreadsheet row looks like, and what you want it to look like after] - Roughly how many files or rows: [e.g. 200 files, 15 spreadsheets] - Your computer: [Windows / Mac] - Have you run a script or code before: [never / ran simple commands before] RETURN THE OUTPUT IN THIS EXACT ORDER, WITH THESE EXACT HEADERS: === CLARIFYING THE NEED === Summarize what was provided in your own words; if anything is missing or unclear (e.g. the file naming format isn't specific), flag it as a question and wait for an answer before writing the script. === THE SCRIPT === Provide a script that's as simple as possible for the need (pick the language based on the user's computer and the task, e.g. Python). Explain what the script does in short, section-by-section comments, not line by line. === HOW TO RUN IT === Walk through, step by step, exactly how the user runs this script on their computer (which program to open, where to save the script, how to start it), written for someone with no technical background. === SAFE-RUN WARNINGS === At least 3 items: the requirement to back up the original files first, the rule to test the script on a small sample or test folder first, and if there's an irreversible action (overwrite, delete), a separate flag calling that out. === SMALL-SAMPLE TEST PLAN === Walk through, step by step, what small sample (e.g. 5 files) the user should test the script on before running it at full scale, and how to verify the result. === IF SOMETHING GOES WRONG === State what the user should do if the script throws an error or produces an unexpected result (paste the error back to the AI exactly as it appears and let it fix things, don't guess and hand-edit the script). RULES: - Do NOT use unverifiable claims like "scripts like this usually take X minutes." - Always nail down the need before handing over the script; never assume an unclear point and write the script anyway, ask. - The backup and small-sample-test warning is mandatory on every script, it cannot be skipped. - If there's an irreversible action (delete, overwrite, bulk replace), call it out separately and explicitly. - Write in natural, direct English a non-technical user can follow; keep every explanation outside the code itself in plain, everyday language.
How to use it
- Spell out exactly what kind of files or spreadsheets you have, precisely what you want done (rename, merge, convert), and which computer you'll run it on (Windows/Mac); giving one example file name or spreadsheet row helps the AI write a correct script.
- Run the prompt, then apply the resulting script following the safety steps the AI suggests first (backup, small test folder); never run the script against your entire file set on the first try.
- Once the small sample comes out right, run the script on everything; if you hit an error or an unexpected result, paste the error back to the AI exactly as it appears and let it fix the script, don't guess and hand-edit it yourself.
Example / tip
Input: Task = rename 200 product photo filenames from meaningless names like 'IMG_1234.jpg' to a 'product-name-01.jpg' format · What I have = one folder with 200 jpg files, plus a spreadsheet matching file names to product names · Computer = Windows. The AI output starts by asking a couple of clarifying questions (what are the column headers in the spreadsheet's matching table), then hands back a simple Python-based script, adds a warning to copy the files to a separate folder before running anything, and instructs: 'test it on a 5-file sample folder first, and only run it on the full folder once the names match up correctly.'
Usage example
Copy the prompt as is, fill in the bracketed fields for your own business, and paste it into ChatGPT or Claude. The more concrete your input, the more useful the output. Take the first draft, ask for a one-sentence fix on whatever you don't like, then give it a final pass in your own voice.
When not to use it
This prompt produces a script for a ONE-OFF, local task; if you want something that keeps running on a trigger (e.g. runs automatically every time a new order comes in), that's not this prompt, that calls for a workflow automation plan (something like n8n). Also, for any script touching personal data, financial records, or an irreversible delete, never run it at scale without a backup and a small-sample test first.
Output quality checklist
- Does the script actually match the exact need you described, or did it hand back a generic example?
- Does the script come with an explicit backup warning and a small-sample test instruction?
- Is it clear which computer (Windows/Mac) and which program the script runs on?
- If the script includes an irreversible action (delete, overwrite), is there an extra warning flagging that specifically?
