When should you use it?
- Your files are spread across a laptop, a cloud drive, email and apps
- Your agent keeps asking where things are or guessing wrong
- You want a starting point before reorganizing files for a team
Not for: Putting passwords, account numbers or client secrets into the map; Letting the agent open, move or delete files during mapping; Replacing proper access controls on shared drives
What do you need, and what do you get?
You need
- A desktop agent that can see the folders or drives you share with it
- Five minutes to answer a few questions about your business and where else work lives
You get
- A one-page CLAUDE.md (or AGENTS.md) in your top folder listing what the business does and where each kind of work lives
- A list of knowledge that is not written down yet
- A walk-test result showing whether the agent can prep a real task using the map
How does it work, step by step?
- Share foldersGive the agent your main working folder, plus any cloud drive you rely on through its connector settings.
- Run the mapping promptThe agent reads names only, asks you about your business and the places it cannot see, then drafts the map for your review.
- Save the mapName it CLAUDE.md for Claude, or AGENTS.md for Codex, Cursor and similar tools.
- Walk testAsk for a real job such as prep for tomorrow's client call. If it gets stuck, add one line to the map saying where that thing lives.
- Consolidate laterOptionally move files into one drive area by area, copying first and deleting old copies only after you check.
The prompt
The original prompt by u/jonathanmalkin, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Claude Cowork, Claude and Claude Code. Values in lime are placeholders.
Original prompt by u/jonathanmalkin
I want to make a map of my work so an AI assistant can find things on its own. 1. Look through the folders and drives I've shared with you. Read the file and folder names only. Don't open, move, change or delete anything. 2. Then ask me these questions, one at a time: - What does my business do, in one sentence? - Where else does my work live that you can't see? For example email, texts, Slack, a CRM, my phone or paper. - Optional: what do people here know that isn't written down anywhere? 3. Write a one-page file called CLAUDE.md in the top folder, in plain English, with: - What the business does - Where each kind of thing lives - What isn't written down yet Show me the file before you save it.
Exactly as published by u/jonathanmalkin in A new hire can ask around. An AI agent can't. The fix is a one-page map of where your work lives (10-minute prompt inside).
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Build a short orientation file so you can find my work without asking me each time. 1) Using only the shared folders and drives, look at names of files and folders. Do not open, move, rename or delete anything. 2) Ask me, one at a time: what my business does in a sentence; which places hold work you cannot see (for example {other_places}); and, optionally, what people here know that is not written anywhere. 3) Draft a one-page plain-English file named {map_filename} for the top folder covering: the business in one line, where each type of work is kept, and gaps that are not documented yet. Leave out passwords, account numbers and client secrets. 4) Show it to me before saving. Then try this test job using only the file: {test_job}. Tell me where you got stuck so I can add a line.
What can go wrong?
- File names can reveal private client details. Review the map before saving or sharing it.
- A map goes stale. Update a line whenever a walk test fails or a tool changes.
- Two copies of the same fact will drift; point to one home instead.
Our take
Most frustration with desktop agents is not about intelligence; it is about orientation. A new employee spends a week learning where contracts, invoices and client notes live. An agent never gets that week, so it guesses or stalls. Malkin's fix is modest and practical: a read-only pass over file and folder names, a few questions about what lives outside the computer, and a one-page map the agent reads first. The read-only limit matters. Nothing is opened, moved or deleted, which makes this a safe first step for someone just starting with Cowork or a similar tool. The walk test is the part we would not skip. Asking for a real first-week job, like call prep, shows quickly whether the map is useful, and each failure becomes one new line instead of a long rewrite. Keep sensitive details out of the map itself; it should say where things live, not copy what they contain. In our dry run with a fictional consultancy's folder tree (clients, proposals, invoices, a stray downloads folder) and answers saying contracts live in email and the CRM holds contacts, the agent produced a 24-line map, listed pricing exceptions as unwritten knowledge, and passed a mock client-call prep test after one added line about where signed contracts live.
Where the time goes back: Ten minutes of mapping saves the repeated back-and-forth of telling an agent where things are, and makes every later task start in the right place.
FAQ
Does the agent read my documents?
What if I use a different agent?
Is this useful for a team?
Source and credit
The original prompt on this page is by u/jonathanmalkin, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- A new hire can ask around. An AI agent can't. The fix is a one-page map of where your work lives (10-minute prompt inside)
- Creator
- u/jonathanmalkin on r/AI_Agents
- Published on
- Original date
- Oct 24, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Claude Cowork
- AI dry run
- Oct 26, 2026: passed. Dry-run tested by our AI test agent on sample input. Read-only mapping; map reviewed before save; walk test passed after one line.
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 26, 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.