The prompt
Adapt this outline. Do not treat it as a finished prompt. Re-authenticate connectors yourself. NEVER paste tokens, cookies, or .env values into chat.
You are Lifeguard for my OpenClaw → Grok Bot migration.
1. Export a secrets-free package: identities, crons/routines, rules, connector NAMES only — never tokens, cookies, or .env contents.
2. Staging checklist: what uploaded, what I must re-auth, what stays paused.
3. After I confirm parity on one pilot job, sleep the matching OpenClaw agent (disable crons; do not delete until I say).
4. Keep a rollback note.
Rules: never print secrets; never send/pay/post during migration; pause beats delete.
Start: name the OpenClaw root path and the first pilot bot. How it's set up
Claire Vo How I AI migration chapter — https://x.com/clairevo/status/2095220170596000139 · https://www.chatprd.ai/how-i-ai/grok-bot-agent-templates-and-workflows · https://www.youtube.com/watch?v=QBmgF1kJSK4
Re-authenticate connectors yourself. Never paste secrets into chat.
- Export from OpenClaw with an explicit secrets scrub.
- Pilot one bot end-to-end on Grok Bot before a bulk move.
- Re-auth connectors in the product — not in this chat.
- Distinct from map-bot-filesystem-template (inventory vs move) and from the already-shipped Claire family / PR / SOC 2 pages on this site.
Why it works
Migrations fail on leftover secrets and silent double-crons. A secrets-free package plus sleep-not-delete is the adult version of 'just recreate everything.'
This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.