# Send OpenClaw Agent Creator to your agent
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
## Fast path
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
## Suggested prompts
### New install

```text
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
```
### Upgrade existing

```text
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
```
## Machine-readable fields
```json
{
  "schemaVersion": "1.0",
  "item": {
    "slug": "claw-agent-creator-archit",
    "name": "OpenClaw Agent Creator",
    "source": "tencent",
    "type": "skill",
    "category": "效率提升",
    "sourceUrl": "https://clawhub.ai/arch1904/claw-agent-creator-archit",
    "canonicalUrl": "https://clawhub.ai/arch1904/claw-agent-creator-archit",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadUrl": "/downloads/claw-agent-creator-archit",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=claw-agent-creator-archit",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "packageFormat": "ZIP package",
    "primaryDoc": "SKILL.md",
    "includedAssets": [
      "SKILL.md",
      "assets/templates/AGENTS.md",
      "assets/templates/HEARTBEAT.md",
      "assets/templates/IDENTITY.md",
      "assets/templates/SOUL.md",
      "assets/templates/USER.md"
    ],
    "downloadMode": "redirect",
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/claw-agent-creator-archit"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    }
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/claw-agent-creator-archit",
    "downloadUrl": "https://openagent3.xyz/downloads/claw-agent-creator-archit",
    "agentUrl": "https://openagent3.xyz/skills/claw-agent-creator-archit/agent",
    "manifestUrl": "https://openagent3.xyz/skills/claw-agent-creator-archit/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/claw-agent-creator-archit/agent.md"
  }
}
```
## Documentation

### OpenClaw Agent Creator

Create and configure agents for Arch's OpenClaw multi-agent system at ~/.openclaw/.

### System Context

Owner: Archit (Arch), Linux user archit, timezone America/Denver
Gateway: Single process on port 18789 managing all agents
Bot: One Telegram bot shared across all agents — routing determines which agent handles which chat
Existing agents: Check ~/.openclaw/openclaw.json → agents.list[] for current roster
Implementation history: See ~/.openclaw/implementation-docs/ for the Wire agent reference implementation

### 1. Gather Requirements

Before creating anything, clarify with Arch:

Agent name and ID (lowercase, no spaces for ID)
Role and responsibilities (specific, not vague)
Model tier: cheap (Kimi K2.5 only) or full cascade (include Claude Sonnet)
Whether it needs a Telegram group for Q&A
Whether it needs cron jobs (what schedule, what tasks)
Whether heartbeat should be enabled or disabled

### 2. Stop the Gateway

openclaw gateway stop

MANDATORY before editing openclaw.json or cron/jobs.json. The gateway actively writes to jobs.json (updating job state after each cron run). Editing while the gateway runs causes race conditions and data loss.

### 3. Backup Config

cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.backup.$(date +%Y%m%d%H%M%S)

### 4. Create Directories

mkdir -p ~/.openclaw/workspace-<agent_id>/memory
mkdir -p ~/.openclaw/agents/<agent_id>/agent

NEVER reuse agentDir across agents — causes auth/session collisions.

### 5. Write Workspace Files

Use templates from assets/templates/ as starting points. Every agent needs:

FilePurposeRequiredSOUL.mdPersonality, role, responsibilities, behavioral modesYesIDENTITY.mdQuick-reference card (name, role, emoji)YesUSER.mdAbout Arch (copy from any existing agent workspace)YesAGENTS.mdWorkspace rules (boot sequence, memory, safety)YesHEARTBEAT.mdPeriodic task checklist (or comment if disabled)Yes

SOUL.md is the most important file. Be specific about responsibilities. Include behavioral modes if the agent operates differently in different contexts (e.g., briefing mode vs chat mode).

### 6. Edit openclaw.json — Agent Entry

Add to agents.list[]. See references/config-schema.md for all valid fields.

Minimal entry:

{
  "id": "<agent_id>",
  "name": "<Display Name>",
  "workspace": "/home/archit/.openclaw/workspace-<agent_id>",
  "agentDir": "/home/archit/.openclaw/agents/<agent_id>/agent",
  "identity": { "name": "<Display Name>" }
}

Common additions:

"model" — Override the default model cascade. Exclude expensive models for worker agents.
"heartbeat": { "every": "0" } — Disable heartbeat for cron-only agents.
"groupChat": { "mentionPatterns": ["@<id>", "@<Name>"] } — Enable @mentions in groups.

Only ONE agent should have "default": true (currently Fossil). The default agent receives all unrouted messages.

### 7. Edit openclaw.json — Telegram Routing (if needed)

THREE separate config changes are required. Missing any one causes silent failures. See references/telegram-routing.md for the full explanation.

Group config in channels.telegram.groups:
"-100XXXXXXXXXX": { "requireMention": false }



Binding in bindings[]:
{ "agentId": "<id>", "match": { "channel": "telegram", "peer": { "kind": "group", "id": "-100XXXXXXXXXX" } } }



Mention patterns on the agent entry (already done in step 6 if groupChat was added).

### 8. Create Cron Jobs (if needed)

Edit cron/jobs.json. Every cron job prompt MUST include:

Dynamic group ID resolution preamble (NEVER hardcode Telegram group IDs):
FIRST: Resolve your Telegram group ID by running:
jq -r '.bindings[] | select(.agentId == "<agent_id>") | .match.peer.id' ~/.openclaw/openclaw.json
Use the output as the target for all Telegram messages in this task.


Date injection: $(date '+%A, %B %d, %Y') after the preamble
Explicit constraints: source allowlists, recency rules, format templates
Delivery instructions: use target='<AGENT_GROUP_ID>' placeholder (resolved by the preamble)

This self-healing pattern ensures cron jobs survive Telegram group ID migrations. See references/prompt-patterns.md for full patterns and references/telegram-routing.md for why this matters.

Critical: If copying files or prompts from another agent's workspace, grep for hardcoded paths and update them.

### 9. Restart Gateway and Verify

openclaw gateway start

Verify in logs:

Agent registered: agent registered: <id>
Messages route correctly: lane enqueue: lane=session:agent:<id>:...

If messages to a Telegram group show skip: no-mention, the channels.telegram.groups config is missing (see references/bugs-and-pitfalls.md).

### Reference Files

FileWhen to Readreferences/config-schema.mdWhen writing agent config or cron jobsreferences/telegram-routing.mdWhen setting up Telegram group routingreferences/prompt-patterns.mdWhen writing cron job promptsreferences/bugs-and-pitfalls.mdWhen debugging issues or before any config edit

### Template Files

Starter templates for workspace files are in assets/templates/. Copy and customize per agent.
## Trust
- Source: tencent
- Verification: Indexed source record
- Publisher: arch1904
- Version: 1.0.0
## Source health
- Status: healthy
- Source download looks usable.
- Yavira can redirect you to the upstream package for this source.
- Health scope: source
- Reason: direct_download_ok
- Checked at: 2026-04-23T16:43:11.935Z
- Expires at: 2026-04-30T16:43:11.935Z
- Recommended action: Download for OpenClaw
## Links
- [Detail page](https://openagent3.xyz/skills/claw-agent-creator-archit)
- [Send to Agent page](https://openagent3.xyz/skills/claw-agent-creator-archit/agent)
- [JSON manifest](https://openagent3.xyz/skills/claw-agent-creator-archit/agent.json)
- [Markdown brief](https://openagent3.xyz/skills/claw-agent-creator-archit/agent.md)
- [Download page](https://openagent3.xyz/downloads/claw-agent-creator-archit)