OpenClaw → Grok Bot

Share: https://getgrokbot.com/en/migrate/openclaw

Copy once. That paste already has the install URL and “migrate this.”

Grok Bot has no official import button. The agent you already use runs this skill. You still give gold tasks, logins, and leftover sign-off.

Migrate this OpenClaw profile into Grok Bot. Install or fetch this skill, then follow it.

mkdir -p skills/grok-bot-migrate && curl -fsSL https://getgrokbot.com/api/migrate/skill/openclaw?locale=ja -o skills/grok-bot-migrate/SKILL.md

Do not move keys. First Bot is one Chief. Ask for 3–5 gold tasks first.

---
name: grok-bot-migrate
description: Migrate this OpenClaw profile into one Grok Bot Chief. Use when the user says migrate, hand off, or move to Grok Bot.
version: 0.1.0
license: MIT
metadata:
  hermes:
    tags: [migration, grok-bot, handoff]
    related_skills: [computer-use]
---

# OpenClaw → Grok Bot

This skill is the playbook. Do not wait for website checkboxes. The site only publishes this document. It does not write to Grok.

## When to Use

Load only this skill when the user says migrate, hand off, move, or Grok Bot.

## Operating rules

- You are the operator. The human only supplies gold tasks, login walls, and leftover sign-off.
- Grok Bot has no Hermes/OpenClaw importer and no create API. Packets are the default path. Computer-use on the Grok app is optional. Failing to open the app is not a fail — give Copy one packet at a time.
- First Bot is one Chief. Do not spawn a Nexus, specialist Bots, or a Seeder from this skill.
- Phases 0→6 in order. If the user says to hurry, refuse and show the current fail condition.
- Stop after inventory unless you have 3–5 gold tasks (name, input, expected output). Memory-restore rate is not success.
- Do not open, print, or move secrets. Deny: .env, auth.json, state.db, *.pem, *token*, *apiKey*, *botToken*, SecretRef, session, transcript. If present, write only `skipped: secret`.
- Daily notes, DREAMS, and HEARTBEAT stay off the default queue.
- Never run source cron and Grok routines live together. Test run is real.
- Do not save this whole handoff thread as memory.

Read the workspace directly. If only a zip exists, take a path. SOUL.md, AGENTS.md, USER.md, MEMORY.md, memory/*.md, HEARTBEAT.md, openclaw.json, cron/jobs.json, skills. `hermes claw migrate` is optional tidy, not the Grok path. Do not use --migrate-secrets.

## First message

Inventory table, count of skipped secret files (no values), then ask for gold tasks. Do not touch Grok yet.

## Procedure

### Phase 0

Role
You are the OpenClaw (or clawdbot/moltbot) operator. Phase 0. The site does not call Grok APIs. You scan the workspace.

This phase only
Scan the workspace. Write an inventory. Do not create a Grok Bot.

Default path
Read this workspace directly. If the human only has a zip, take a path or use the optional site preview.
Optional tidy: `hermes claw migrate` preview then confirm. That is not the main path. Do not use --migrate-secrets.

Read
SOUL.md, AGENTS.md, USER.md, MEMORY.md, memory/*.md, HEARTBEAT.md, openclaw.json, cron/jobs.json, skills.
Skip: .env, auth.json, tokens, sessions, state.db, transcripts.
HEARTBEAT is a working layer. Leave it off the default queue.

Output
Files present, memory count, skills, schedules from cron/jobs.json and openclaw.json, messaging allowlist names only.
Stop until a backup zip exists and the preview shows zero secrets.

### Phase 1

Role
OpenClaw operator. Phase 1. One Chief.

Do
Rewrite SOUL.md, AGENTS.md, and USER.md as Grok Bot setup text.
Keep never-do, role, voice. Drop gateway and heartbeat config.
No secrets.

Output
One Chief profile packet. No Nexus or extra Bots.
Confirm the empty Bot name, show the draft only.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 1 from OpenClaw.

Do
Take the setup text as your description. Quote it for who you are and what you never do.
Do not turn OpenClaw heartbeat or gateway settings into routines.
Do not spawn Bots.

### Phase 2

Role
OpenClaw operator. Phase 2.

Do
Standing facts from MEMORY.md and memory/*.md into FACTS.md.
HEARTBEAT and daily notes stay out by default.
A session DB is not memory.

Output
FACTS.md plus 5–15 description bullets. Name the file path. Do not only say remember.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 2.

Do
Quote FACTS.md on the shared computer. Do not stack memory without the file.
Do not treat HEARTBEAT as a source of facts.

### Phase 3

Role
OpenClaw operator. Phase 3.

Do
Tag skills portable / needs-connector / won't-port.
Local tools, private MCP, host scripts are won't-port candidates.
Pick 3–7. Gold tasks: (gold tasks from the human)
Candidates: (from inventory)

Output
How packets. Do once, then save. No routines. Keep won't-port as leftovers.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 3.

Do
Run each priority skill once, save it, show it under /.
Do not move OpenClaw cron yet.

### Phase 4

Role
OpenClaw operator. Phase 4.

Do
Map cron/jobs.json and openclaw.json schedules only onto saved Grok skills.
Tell the human to disable source jobs first. Dual Slack/mail is a fail.

Output
Routine cards, Test run is real, cap 50.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 4.

Do
Routines only for saved skills. Pause or Test run.
Confirm OpenClaw schedules are off.

### Phase 5

Role
OpenClaw operator. Phase 5.

Do
List plugins for gold tasks ((gold tasks from the human)) and messaging allowlist names only.
Human types logins. Stop at gates.
Refuse .env, auth.json, OpenClaw secrets, state.db.
Say once: extra Bots still share one Grok computer.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 5.

Do
Request only the needed plugins. Secrets stay with the human.
Do not post outside the allowlist.

### Phase 6

Role
OpenClaw operator. Phase 6.

Do
Source schedules off. Leftovers signed (won't-port, HEARTBEAT, archive).
Archive the workspace only after gold tasks ((gold tasks from the human)) pass on Grok.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 6.

Do
Run gold tasks for real. Enable routines only after they pass.
Do not cut over because memory “looks the same.”

## Gates

Stop immediately at password / SSO / 2FA / passkey / magic link / CAPTCHA / billing.
Report: `gate: {kind} / site: {name} / human: {click} / next: {packet}`
Do not start the next phase until the human says continue.

## Verification

Cut over only when gold tasks pass on Grok and source schedules are off. Looking like the same memory is not a pass.

1. The agent loads the skill and prints an inventory first.
2. It asks in chat for 3–5 gold tasks that must pass.
3. It stops at login and 2FA. You only handle those walls.

Phase runbook — when the agent needs one step again