OpenClaw Growth Pack

---

name: openclaw-growth-pack

description: Turn a fresh OpenClaw install into a reliable execution agent. Use when users report "asks step-by-step only", stalls mid-task, token mismatch, or model routing/auth failures. Apply a production onboarding baseline: model routing, gateway token consistency, anti-stall heartbeat, lightweight autonomy loop, and verification checklist.

---

# OpenClaw Growth Pack

Apply this skill to bootstrap a new OpenClaw instance into a stable, task-completing setup.

Use this workflow in order:

1. Align model routing and provider endpoint.

2. Align gateway token values across runtime surfaces.

3. Install anti-stall execution contract in `AGENTS.md` and `HEARTBEAT.md`.

4. Enable lightweight periodic self-check.

5. Run verification gates before calling setup complete.

Keep changes minimal, auditable, and reversible.

1) Model Routing Baseline

Use one source of truth in `~/.openclaw/openclaw.json`:

{
  "models": {
    "mode": "merge",
    "providers": {
      "bailian": {
        "baseUrl": "https://coding.dashscope.aliyuncs.com/v1",
        "apiKey": "YOUR_CODING_PLAN_KEY"
      }
    }
  },
  "agents": {
    "defaults": {
      "model": {
        "primary": "bailian/qwen3-coder-plus"
      }
    }
  }
}

Rules:

2) Gateway Token Consistency

Keep all token surfaces aligned:

PowerShell audit:

$cfg = Get-Content "$HOME/.openclaw/openclaw.json" -Raw | ConvertFrom-Json
$auth = $cfg.gateway.auth.token
$remote = $cfg.gateway.remote.token
"auth.token   = $auth"
"remote.token = $remote"
if ($remote -and $auth -ne $remote) { Write-Warning "Token mismatch in openclaw.json" }

After any token change:

openclaw gateway restart

3) Anti-Stall Contract

Write or update `AGENTS.md` with these mandatory constraints:

Write or update `HEARTBEAT.md`:

4) Lightweight Autonomy Loop

If cron/system events are available, create conservative jobs:

If cron is unavailable, enforce manual equivalent:

5) Verification Gates (Do Not Skip)

Setup is complete only when all pass:

Recommended evidence:

6) Rollback

Before edits, create backups:

Copy-Item "$HOME/.openclaw/openclaw.json" "$HOME/.openclaw/openclaw.json.bak" -Force

Rollback:

Copy-Item "$HOME/.openclaw/openclaw.json.bak" "$HOME/.openclaw/openclaw.json" -Force
openclaw gateway restart

References

For concrete command examples and troubleshooting playbooks, read: