Do not start with a giant system.
Give Cowork one contained job. A folder to read, a result to create, and a clear way for you to review what changed.
Open the Claude desktop app
Use the desktop app because Cowork is built for local work, files, folders, and your actual working environment.
Choose one safe folder
Pick a small project folder with notes, drafts, or files you already understand. Do not start with your whole computer.
Ask for an outcome, not advice
Try: "Read this folder and create a short workspace summary with the key files, open questions, and next actions."
Review what changed
Look at the files, check the logic, and ask for a revision. The review loop is what turns Cowork from impressive into useful.
Save the pattern
If the workflow worked, turn the instructions into a repeatable habit, skill, or scheduled task later.
The first skill is not prompting. It is knowing what done looks like.
Use guardrails before you use power.
Start read-only when you are nervous
Ask Cowork to inspect, summarize, and recommend before asking it to reorganize or create files.
Name the output format
Tell it whether you want a checklist, summary, report, spreadsheet, folder structure, or draft.
Ask for an audit trail
When files move or change, ask Cowork to leave a short note explaining what it did and why.
Keep humans in the final review
Cowork can do the heavy lift. You still decide what gets sent, published, or trusted.
People ask Cowork questions when they should assign work.
Instead of "Can you help me organize this?" say what you want the folder to look like when the job is finished.
"Help me with these files."
The request is vague, so Cowork has to guess the job.
"Read this folder, group the files by project stage, create a short index, and flag anything that looks duplicated."
The job has context, output, and review criteria.