← Back to library

Give your agent a one-page map of where your work lives

On r/AI_Agents, u/jonathanmalkin explains why agents stall in a new business (they cannot ask around) and shares a read-only prompt that builds a one-page map of where each kind of work lives, plus a walk test to check it. We add how to use it with a team and what to keep out of the map.

  • OutcomeIn about ten minutes, have a desktop agent read only your folder and file names, interview you about what it cannot see, and write a one-page CLAUDE.md or AGENTS.md map it reads before every job.
  • SetupMinutes
  • LevelStarter
  • Creditu/jonathanmalkin on r/AI_Agents
View original
Works with
Claude CoworkClaudeClaude Code

Published Oct 26, 2026Updated Oct 26, 2026AI dry run on sample input: passed Oct 26, 2026Source verified Oct 26, 2026

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?

  1. Share foldersGive the agent your main working folder, plus any cloud drive you rely on through its connector settings.
  2. 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.
  3. Save the mapName it CLAUDE.md for Claude, or AGENTS.md for Codex, Cursor and similar tools.
  4. 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.
  5. 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

Word for wordby 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)

Adapted prompt3 variables
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?
Not during mapping. The prompt limits it to file and folder names, and it shows you the map before saving.
What if I use a different agent?
Save the same text under the filename AGENTS.md instead. Many coding and desktop agents look for that file automatically.
Is this useful for a team?
Yes. Keep one shared map in the drive everyone uses, plus a short rules file for tone and approvals.

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
Reddit
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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminSkill✓ AI dry run

Have Claude fill PDF forms, even ones with no fields

Give Claude the pdf skill so that when you hand it a form and the answers, it first checks whether the file has real form fields, fills those by their IDs if it does, places text by measured coordinates on flat or scanned forms if it does not, validates every box before writing, and renders the filled pages as images so you can see where each answer landed before you sign or send it.

Credit: Anthropic

Minutes
Operations & AdminPrompt✓ AI dry run

Brief an agent with nine fields, not a how-to

Before you hand a job to an agent, fill in nine short fields that name the result, the sources it may use, the deadline, what it may do alone, what needs your say-so, what it must never do, how to prove the work is finished, what to do when it gets stuck, and where to put the deliverable, then add a line that tells it to pick the simplest reliable method.

Credit: Michael Fenech (@Michael_Fenech_)

Minutes
Operations & AdminPrompt✓ AI dry run

Check saved agent skills hold up on a messier second run

Have your lead agent list every private skill it can reach, check each one for a clear purpose, required inputs, decision rules, a way to verify results, a defined output, approval points, failure handling and protection against duplicate actions, then draft improved instructions and a tougher test for your approval.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminSkill✓ AI dry run

Diagnose a down machine from its history, sensors and manual

Use the breakdown-diagnosis skill from Anthropic's Claude for Manufacturing plugin to put any safety hazard first, read the sensor trace before the stoppage, search the asset's work orders and technician notes, check the manufacturer's troubleshooting guide, and get ranked likely causes with the quickest test to tell them apart plus a draft preventive maintenance change.

Credit: anthropics

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Drive desktop apps when an integration is blocked

Get work done through apps you cannot connect by API, by letting an agent control your desktop and operate them the way you would, with you approving sends.

Credit: Prasid

Under an hour