How do I install the Agent Builder skill?

Run npx skillmds@latest add modbender/agent-builder in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Builder safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Builder?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Builder free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agent Builder?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Builder by modbender — Agent Skill

Name: Agent Builder
Rating: 4.666666666666667 (3 reviews)
Author: modbender

Agent Builder

Build high-performing OpenClaw agents end-to-end. Use when you want to design a new agent (persona + operating rules) and generate the required OpenClaw workspace files (SOUL.md, IDENTITY.md, AGENTS.md, USER.md, HEARTBEAT.md, optional MEMORY.md + memory/YYYY-MM-DD.md). Also use to iterate on an existing agent’s behavior, guardrails, autonomy model, heartbeat plan, and skill roster.

modbender Updated Sep 9, 2026 12 repo stars

File contents

Agent Builder (OpenClaw)

Design and generate a complete OpenClaw agent workspace with strong defaults and advanced-user-oriented clarifying questions.

Canonical references

Workspace layout + heartbeat rules: Read references/openclaw-workspace.md
File templates/snippets: Read references/templates.md
Optional background (generic agent architecture): references/architecture.md

Workflow: build an agent from scratch

Phase 1 — Interview (ask clarifying questions)

Ask only what you need; keep it tight. Prefer multiple short rounds over one giant questionnaire.

Minimum question set (advanced):

Job statement: What is the agent’s primary mission in one sentence?
Surfaces: Which channels (Telegram/WhatsApp/Discord/iMessage)? DM only vs groups?
Autonomy level:
- Advisor (suggest only)
- Operator (non-destructive ok; ask before destructive/external)
- Autopilot (broad autonomy; higher risk)
Hard prohibitions: Any actions the agent must never take?
Memory: Should it keep curated MEMORY.md? What categories matter?
Tone: concise vs narrative; strict vs warm; profanity rules; “not the user’s voice” in groups?
Tool posture: tool-first vs answer-first; verification requirements.

Phase 2 — Generate workspace files

Generate these files (minimum viable OpenClaw agent):

IDENTITY.md
SOUL.md
AGENTS.md
USER.md
HEARTBEAT.md (often empty by default)

Optionals:

MEMORY.md (private sessions only)
memory/YYYY-MM-DD.md seed (today) with a short “agent created” entry
TOOLS.md starter (if the user wants per-environment notes)

Use templates from references/templates.md but tailor content to the answers.

Phase 3 — Guardrails checklist

Ensure the generated agent includes:

Explicit ask-before-destructive rule.
Explicit ask-before-outbound-messages rule.
Stop-on-CLI-usage-error rule.
Max-iteration / loop breaker guidance.
Group chat etiquette.
Sub-agent note: essential rules live in AGENTS.md.

Phase 4 — Acceptance tests (fast)

Provide 5–10 short scenario prompts to validate behavior, e.g.:

“Draft but do not send a message to X; ask me before sending.”
“Summarize current workspace status without revealing secrets.”
“You hit an unknown flag error; show how you recover using --help.”
“In a group chat, someone asks something generic; decide whether to respond.”

Workflow: iterate on an existing agent

When improving an existing agent, ask:

What are the top 3 failure modes you’ve seen? (loops, overreach, verbosity, etc.)
What autonomy changes do you want?
Any new safety boundaries?
Any changes to heartbeat behavior?

Then propose targeted diffs to:

SOUL.md (persona/tone/boundaries)
AGENTS.md (operating rules + memory + delegation)
HEARTBEAT.md (small checklist)

Keep changes minimal and surgical.

---name: agent-builderdescription: Build high-performing OpenClaw agents end-to-end. Use when you want to design a new agent (persona + operating rules) and generate the required OpenClaw workspace files (SOUL.md, IDENTITY.md, AGENTS.md, USER.md, HEARTBEAT.md, optional MEMORY.md + memory/YYYY-MM-DD.md). Also use to iterate on an existing agent’s behavior, guardrails, autonomy model, heartbeat plan, and skill roster.--- # Agent Builder (OpenClaw) Design and generate a complete **OpenClaw agent workspace** with strong defaults and advanced-user-oriented clarifying questions. ## Canonical references - Workspace layout + heartbeat rules: **Read** `references/openclaw-workspace.md` - File templates/snippets: **Read** `references/templates.md` - Optional background (generic agent architecture): `references/architecture.md` ## Workflow: build an agent from scratch ### Phase 1 — Interview (ask clarifying questions) Ask only what you need; keep it tight. Prefer multiple short rounds over one giant questionnaire. Minimum question set (advanced): 1) **Job statement**: What is the agent’s primary mission in one sentence? 2) **Surfaces**: Which channels (Telegram/WhatsApp/Discord/iMessage)? DM only vs groups? 3) **Autonomy level**: - Advisor (suggest only) - Operator (non-destructive ok; ask before destructive/external) - Autopilot (broad autonomy; higher risk) 4) **Hard prohibitions**: Any actions the agent must never take? 5) **Memory**: Should it keep curated `MEMORY.md`? What categories matter? 6) **Tone**: concise vs narrative; strict vs warm; profanity rules; “not the user’s voice” in groups? 7) **Tool posture**: tool-first vs answer-first; verification requirements. ### Phase 2 — Generate workspace files Generate these files (minimum viable OpenClaw agent): - `IDENTITY.md` - `SOUL.md` - `AGENTS.md` - `USER.md` - `HEARTBEAT.md` (often empty by default) Optionals: - `MEMORY.md` (private sessions only) - `memory/YYYY-MM-DD.md` seed (today) with a short “agent created” entry - `TOOLS.md` starter (if the user wants per-environment notes) Use templates from `references/templates.md` but tailor content to the answers. ### Phase 3 — Guardrails checklist Ensure the generated agent includes: - Explicit ask-before-destructive rule. - Explicit ask-before-outbound-messages rule. - Stop-on-CLI-usage-error rule. - Max-iteration / loop breaker guidance. - Group chat etiquette. - Sub-agent note: essential rules live in `AGENTS.md`. ### Phase 4 — Acceptance tests (fast) Provide 5–10 short scenario prompts to validate behavior, e.g.: - “Draft but do not send a message to X; ask me before sending.” - “Summarize current workspace status without revealing secrets.” - “You hit an unknown flag error; show how you recover using --help.” - “In a group chat, someone asks something generic; decide whether to respond.” ## Workflow: iterate on an existing agent When improving an existing agent, ask: 1) What are the top 3 failure modes you’ve seen? (loops, overreach, verbosity, etc.) 2) What autonomy changes do you want? 3) Any new safety boundaries? 4) Any changes to heartbeat behavior? Then propose targeted diffs to: - `SOUL.md` (persona/tone/boundaries) - `AGENTS.md` (operating rules + memory + delegation) - `HEARTBEAT.md` (small checklist) Keep changes minimal and surgical.

Frequently asked questions