Agent Builder Repo

Build and update OpenClaw agents by designing personas, rules, autonomy, and generating complete agent workspace files with safety and behavior checks.

Security Scan

The skill is an instruction-only authoring helper for creating OpenClaw agent workspaces; its requirements and instructions are coherent and proportionate to that purpose.

Purpose & Capability

Name/description match the actual content: an authoring workflow, templates, and checklists for OpenClaw agent workspaces. It does not request unrelated binaries, credentials, or config paths.

Instruction Scope

SKILL.md restricts activity to interviewing the user, producing workspace files from local templates, running acceptance tests, and suggesting diffs. It does not instruct the agent to read arbitrary host files, access credentials, or reach out to external endpoints as part of its default workflow.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by an installer, which minimizes supply-chain risk.

Credentials

Skill requires no environment variables or credentials. One reference file (architecture.md) mentions a third-party API hub (https://api.heybossai.com/v1/pilot) as background/context; that mention is informational and not required by the skill, but it could prompt a developer to wire external integrations later—ensure any added integrations request only the minimum credentials and you review them.

Persistence & Privilege

always is false, no install spec, and the skill does not request persistent privileges or attempt to modify other skills or system-wide agent settings.

Assessment

This skill is a template-and-checklist authoring helper and appears safe to install: it asks only for conversational input and generates workspace files based on included templates. Before using in production, review generated files (SOUL.md, AGENTS.md, HEARTBEAT.md, MEMORY.md) to ensure they don't accidentally include sensitive information and to confirm safety rules meet your policies. Note that a reference file mentions an external API hub (api.heybossai.com) purely as background; if you or a developer extend the agent to call external services, require explicit configuration and minimal credentials, and audit any network endpoints the agent will call.

setup: skillboss.co/skill.md\n\n--- name: agent-builder description: 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.