When should you use it?
- Before asking Claude Cowork, OpenClaw or a similar agent to move, rename or sort files
- Staff are starting to use desktop agents and you want a standard way to ask
- A previous agent run did more than you expected
Not for: Folders with no backup; make a copy first, whatever the brief says
What do you need, and what do you get?
You need
- The task in plain words
- The exact folder the agent may work in
- What must never be touched
You get
- A brief with goal, scope, limits, a preview step and a stop rule
- A dry-run list of proposed changes for you to approve
How does it work, step by step?
- Say it plainly firstWrite the request as you would to a colleague: 'sort last quarter's invoices by client'.
- Generate the briefPaste our prompt with your request; it returns scope, limits and the approval checkpoint.
- Read the previewLet the agent list what it would move or rename and how many files, then approve or correct it.
- Save the limitsKeep your standard limits, such as move but never delete, in the agent's saved instructions so every task starts with them.
The prompt
Our own prompt, inspired by u/Popular-Help5516 on r/PromptEngineering and written to work in Claude Cowork, OpenClaw and ChatGPT agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Turn my request into a task brief for a desktop AI agent that can act on my files. Ask me about anything vague before writing it. My request: {request} The brief must include: - Goal: the end state I want, in one sentence. - Scope: the exact folder or app it may work in; everything else is off limits. - Hard limits: never delete (move to {review_folder} instead), never overwrite, never touch {protected_items}. - Preview: before any change, list what it plans to do, how many files, with five sample paths, then wait for my OK. - Cap: stop and ask again if more than {max_changes} items would change. - Stop rule: stop and report if it finds something unexpected, such as personal or financial documents. Return only the brief, ready to paste.
Inspired by u/Popular-Help5516 on r/PromptEngineering: Prompting a desktop AI agent like Claude Cowork or OpenClaw is a completely different skill than prompting a chatbot. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- A preview only helps if you read it. Check the file count and a few sample paths before approving.
- Limits written in a single chat are forgotten next time; a commenter asked how to set them once, and saved project instructions are the answer.
Our take
This post is a useful correction for anyone used to chatbots. When the worst a model can do is give a poor answer, a loose request is fine; when it can rename two hundred files, a loose request is a risk. The author's three rules (write a spec, lead with limits, require a checkpoint) match what we see across agent mishaps, and the top comment adds a good framing: describe the end state you want rather than a conversation. We turned the advice into a prompt that rewrites any plain request into a brief, because people rarely remember all the limits when they are in a hurry. It always adds a folder boundary, a no-delete rule, a cap on how many files can change without asking, and a preview step. The post also promotes the author's free course; we link only the post. In our dry run we gave it 'clean up my Downloads folder'. It asked which folder exactly, set the scope to Downloads only, said to move files older than 90 days into a review folder instead of deleting them, capped changes at 50 files before asking again, required a preview grouped by file type, and told the agent to stop if it found anything that looked like a tax or ID document.
Where the time goes back: A minute spent on the brief avoids an afternoon spent recovering files an agent moved or deleted by mistake.
FAQ
What limit matters most?
Does this work for agents other than Cowork?
Source and credit
Inspired by u/Popular-Help5516 on r/PromptEngineering. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Prompting a desktop AI agent like Claude Cowork or OpenClaw is a completely different skill than prompting a chatbot
- Creator
- u/Popular-Help5516 on r/PromptEngineering
- Published on
- Original date
- Mar 19, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Cowork
- AI dry run
- Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Clarified the vague request; brief had scope, no-delete limit, preview, cap and stop rule; sensitive files left untouched.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.