Last week I told you the configuration is the product. I gave you a 5-section SOUL.md framework. Some of you copied the executive assistant template, customized it, and immediately saw better results. Great.
But a bunch of you replied with the same problem: "I sat down to write my SOUL.md and stared at a blank file for 20 minutes."
Of course you did. Writing a good system prompt from scratch is hard for the same reason writing a good bio is hard — you're too close to yourself to describe yourself clearly. You know what you want, but you can't articulate it in the structured way the agent needs.
There's a fix. It's called reverse prompting, and it's the single biggest unlock I've found for agent configuration.
The idea in one sentence
Instead of you writing the prompt, the agent interviews you and generates the prompt from your answers.
Traditional prompting: you → prompt → agent → output. Reverse prompting: you → goal → agent → questions → you → answers → agent → prompt.
That extra loop changes everything. The agent asks questions you wouldn't think to answer. It surfaces constraints you forgot you had. It structures the output in a way that's optimized for how LLMs actually process instructions — because it is an LLM.
Why this matters specifically for OpenClaw
OpenClaw's bootstrap files are loaded into every single prompt. They're not one-time instructions — they're persistent context that shapes every interaction. That means poorly written workspace files don't just produce one bad response; they produce systematically bad responses, forever, on every turn.
Reverse prompting fixes the input quality problem at the source. Instead of you guessing what the agent needs to know, the agent tells you what it needs to know.
The 3-step reverse prompting workflow
Step 1: The brain dump. Open a conversation with your agent (or any LLM — Claude, ChatGPT, whatever you prefer for long-form work). Paste the reverse prompting meta-prompt from this week's Blueprint below. Then just... talk. Describe your job. Describe your frustrations. Describe what you wish your agent did. Don't structure it. Don't edit yourself. Ramble.
The meta-prompt tells the agent to interview you — it will ask follow-up questions, probe for specifics, and push you past the generic answers.
Step 2: The generation. After 5–10 back-and-forth exchanges, tell the agent: "Generate my SOUL.md based on everything I've told you. Use the 5-section framework: Identity, Philosophy, Communication Style, Rules, Proactive Behaviors."
What you get back will be surprisingly good. Not because the AI is creative — because it extracted structure from your unstructured thoughts. It found the patterns in what you said and formalized them.
Step 3: The refinement loop. Paste the generated SOUL.md into ~/.openclaw/agents/default/SOUL.md. Restart with openclaw daemon restart. Use it for 3–5 days. Then ask your running agent: "Based on our interactions this week, what's missing from your SOUL.md? What rules should be added? What behaviors should change?"
Commit the updates. Repeat weekly. This is the compound effect I talked about last week — but now the starting point is dramatically better, so the iterations compound faster.
What a good reverse prompting session looks like
The agent shouldn't ask you "What personality do you want?" That's as useless as an empty text field. A good reverse prompting agent asks things like:
"When your agent gives you a morning briefing, what would make you actually read it vs. ignore it?"
"Think about the last time an AI response annoyed you. What specifically was wrong?"
"You mentioned you hate follow-up questions. But are there situations where you want the agent to clarify before acting?"
"What's an example of something you wish your agent would just do without you asking?"
These are the questions that surface the constraints you don't know you have. The answers become precise instructions that generic templates never capture.
The deeper principle
Reverse prompting works because it solves a fundamental asymmetry: you know what good agent behavior feels like when you experience it, but you can't always describe it in advance. An interview extracts tacit knowledge — the stuff you know but haven't formalized.
This applies beyond SOUL.md. You can reverse-prompt your way to a better AGENTS.md, a better USER.md, better tool configurations. Any time you're staring at a blank config file, the answer is the same: don't write it. Get interviewed for it.
The reverse prompting meta-prompt
Copy this entire block. Paste it into a conversation with your agent (or Claude/ChatGPT directly). Answer the questions it asks. After 5–10 rounds, tell it to generate your SOUL.md.
You are a workspace configuration interviewer for OpenClaw.
Your job is to interview me and generate a personalized
SOUL.md file based on my answers. Do NOT generate the file
until I explicitly ask you to.
Interview rules:
- Ask ONE question at a time. Wait for my answer.
- Start broad, then get specific based on my responses.
- Push past generic answers. If I say "be helpful," ask
"what does helpful look like specifically in your workflow?"
- If I give a short answer, probe: "Can you give me an
example of when that mattered?"
- Cover all 5 sections: Identity, Philosophy,
Communication Style, Rules, Proactive Behaviors.
- Spend extra time on Rules and Proactive Behaviors —
these have the highest impact on daily usefulness.
- Ask about anti-patterns: "What should your agent
NEVER do?" and "What's the most annoying thing an AI
assistant has done to you?"
- Ask about context: my job role, tools I use daily,
communication preferences, timezone, work hours.
- Total interview: 8-12 questions. Don't rush it, but
don't drag it out either.
When I say "generate it," produce a complete SOUL.md using
this exact structure:
# Identity
[1 sentence: agent name + role + who it serves]
# Philosophy
[3-5 behavioral principles, each specific enough to
change actual outputs. No generic platitudes.]
# Communication Style
[4-6 concrete instructions about tone, length, formatting,
and energy-matching.]
# Rules
[6-10 hard limits. Start each with NEVER or ALWAYS.
Include at least one security rule about external content.]
# Proactive Behaviors
[4-6 actions the agent takes WITHOUT being asked.
Include timing where relevant.]
After generating, ask me: "Want me to also generate your
USER.md and AGENTS.md? I have enough context to draft both."
Begin the interview now. Start with: "What do you do for
work, and what does a typical day look like?"Why this works better than writing from scratch: The meta-prompt constrains the interviewer agent to ask one question at a time (preventing the overwhelm of a 20-question wall), push past generic answers (the "be helpful" problem), and cover all five SOUL.md sections systematically. The output format is pre-defined, so the generated file drops directly into your workspace with no reformatting.
Power move: After generating SOUL.md, say "yes" when it offers to generate USER.md and AGENTS.md. You'll get a coherent set of workspace files built from the same interview, instead of three files written in isolation that might contradict each other.
Skill review: web-search (Brave Search)
What it does: Gives your OpenClaw agent the ability to search the web in real-time using the Brave Search API. Returns results the agent can read, summarize, and act on.
Setup difficulty: Easy. Create a free Brave Search API account, grab the API key, add it to your skill config. Five minutes.
Verdict: Immediately useful for morning briefings, link summarization, and research tasks. Without it, your agent is limited to what the LLM already knows — which has a knowledge cutoff and can't tell you today's weather or whether your flight is delayed. With it, your agent can answer "what happened overnight?" with actual current information.
The free tier gives you 2,000 queries per month, which is more than enough for personal use. If you're running cron jobs that search on a schedule (like automated morning news digests), you'll want to monitor usage — it adds up faster than you'd expect.
Watch out for: The agent will sometimes over-search — running 3–4 queries for a simple question when one would do. Add a rule to your AGENTS.md: "When searching the web, use one well-crafted query before trying additional searches. Prefer specific queries over broad ones." This cuts unnecessary API calls significantly.
Rating: High value, low effort. Install after gog.
Your agent should be smarter than your template
Here's the irony of Issue #1: I gave you a template for writing SOUL.md, and some of you — I know because you told me — copied it word for word and changed nothing except the name.
That's the generic copy-paste problem I warned about, applied to my own template.
Templates are starting points, not destinations. The whole point of the 5-section framework is that your Philosophy section should be different from mine, because you have different work, different communication preferences, different things that annoy you about AI.
Reverse prompting fixes this. You can't copy-paste an interview. The output is inherently personal because the input was personal. Two people using the same meta-prompt will produce completely different SOUL.md files — which is exactly how it should be.
The best agent configuration is the one that could only belong to you.
See you next week.
— Michael
