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`:

```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:
- Do not keep `coding-intl.dashscope.aliyuncs.com` in active config.
- Do not duplicate provider definitions in multiple files unless strictly needed.
- If `~/.openclaw/agents/main/agent/models.json` exists, remove conflicting provider overrides.

## 2) Gateway Token Consistency

Keep all token surfaces aligned:
- `gateway.auth.token` in `openclaw.json`
- `gateway.remote.token` in `openclaw.json` (if present)
- Dashboard Control UI token (paste the same value)

PowerShell audit:

```powershell
$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 $remo...