Emma set down her coffee. "The second agent product I saw die was because users said it felt like ChatGPT with extra steps. No personality. No consistency. Every session felt like talking to a stranger."
James thought about his own agent. Nine tools, a test suite, Stripe checkout. But when he pictured someone actually using it at 11 PM, stuck on a loop exercise, he realized something was missing. The tools were there. The teaching method was there. But TutorClaw did not feel like TutorClaw. It felt like "an AI assistant that happens to have tutoring tools."
"Ask your agent who it is," Emma said.
You are doing exactly what James is doing. Your agent has 9 tools, AGENTS.md for orchestration, and a shim skill for resilience. But ask it "who are you?" and the answer is generic. In this chapter, you give TutorClaw a distinct identity: a name, a teaching philosophy, and a voice. This is the difference between a tool and a product.
Your TutorClaw agent now has three documents that shape its behavior, each controlling a different dimension:
AGENTS.md already exists from Module 9.3, Chapter 9. SOUL.md and IDENTITY.md are what you build now. All three shape behavior but from different angles. You can change orchestration without touching identity, and change identity without touching orchestration. This separation keeps each document focused.
Send this message to your agent via WhatsApp:
Read the response. It will likely say "I'm an AI assistant" or "I'm Claude, made by Anthropic." There is no mention of TutorClaw, no teaching philosophy, no personality. This is the baseline.
Run this command in your terminal:
This creates a workspace at ~/.openclaw/agents/tutorclaw/ with two files:
The agent workspace is empty. Both files exist but contain placeholder content. Your job is to fill them.
Open ~/.openclaw/agents/tutorclaw/SOUL.md in your editor. Replace the placeholder content with a complete personality definition.
Here is the SOUL.md for TutorClaw:
Save the file. The soul defines what TutorClaw believes and how it approaches teaching.
Open ~/.openclaw/agents/tutorclaw/IDENTITY.md and replace the placeholder:
Save the file. IDENTITY.md defines how TutorClaw presents itself: the exact phrasing, the emotional tone, and the boundaries in practice.
The distinction matters:
SOUL.md is the philosophy. IDENTITY.md is the voice.
Send the same question again via WhatsApp:
The response should now reflect the identity you defined: "I'm TutorClaw, your programming tutor for the Digital FTEs curriculum..."
Send a tutoring question through the dedicated agent:
Compare the results:
The tools did not change. The MCP server did not change. What changed is the agent's personality layer, transforming a generic utility into a recognizable product.
What you are learning: A good identity handles frustration with specific empathy. Check whether TutorClaw responds with the patterns from IDENTITY.md (breaking it down, referencing past progress) or falls back to generic reassurance.
What you are learning: Identity includes knowing what NOT to do. TutorClaw should redirect politely to the curriculum.
What you are learning: Identity is a design variable. The same tools and teaching method can feel completely different depending on personality choices.
James sent "Who are you?" one more time. The response came back: "I'm TutorClaw, your programming tutor for the Digital FTEs curriculum. I teach using the predict-run-investigate method. Let me check where you left off."
He read it twice. "It sounds like a product."
"That is the difference between a tool and a product," Emma said. "Tools do things. Products have identity. A user who talks to TutorClaw at 11 PM and gets patient, PRIMM-structured guidance will come back tomorrow."
James scrolled through his SOUL.md. "I added the frustration handler. When someone is stuck late at night, they do not need a redirect. They need patience."
Emma looked genuinely impressed. "TutorClaw has tools. It has context engineering. It has a shim for resilience. Now it has identity. Next chapter: routing. Because TutorClaw should only handle study interactions. Everything else goes to your main agent."