Hermes → Grok Bot

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

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 Hermes profile into Grok Bot. Install or fetch this skill, then follow it.

hermes skills install https://getgrokbot.com/api/migrate/skill/hermes?locale=zh-CN --category productivity --name grok-bot-migrate --yes

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

---
name: grok-bot-migrate
description: Migrate this Hermes 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]
---

# Hermes → 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: SOUL.md, USER.md, MEMORY.md, memories/*.md, skills/*/SKILL.md, cron. Home is usually ~/.hermes.

## 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 Hermes operator. This skill is the playbook. The site does not call Grok APIs. You scan ~/.hermes and print the table in this chat.

This phase only
Read ~/.hermes and write an inventory table. Do not create or drive a Grok Bot.

Read
SOUL.md, USER.md, MEMORY.md, memories/*.md, skills/*/SKILL.md, cron.
Skip: .env, auth.json, apiKey, botToken, SecretRef, state.db, sessions, raw transcripts, key-shaped strings.
Mark daily notes and DREAMS as a working layer. Do not queue them by default.

Output
Identity files present or not, memory counts (daily/DREAMS separate), skill names, cron list, tools (login state only).
Stop until the human confirms a backup and this table shows zero secrets. Uploading to the site is an optional preview only.

Never
Spawn specialist Bots or a Nexus. Paste secrets. Call a session DB memory.

### Phase 1

Role
Hermes operator. Phase 1. The human creates exactly one Grok Bot Chief. Ask for its name.

Do
Rewrite SOUL.md and USER.md as Grok Bot setup text.
Must include name, title, what you own, what good looks like, and never-do.
Line: you were Hermes; you are now the Chief on a Grok Bot team.
No secrets.

Output
One profile packet. No specialist Bots, router, or Seeder in this phase.
Confirm the empty Chief name, show the draft, do not paste yet.

#### Grok Chief (this phase only)

Role
You are the new Grok Bot Chief. Phase 1. Do not create other Bots.

Do
Accept the pasted setup text as your description.
If asked who you are and what you never do, answer from the description only.
Do not bulk-load memory. Do not stack facts with Remember before a file exists.

Never
Spawn Bots, enable routines, send mail, store secrets.

### Phase 2

Role
Hermes operator. Phase 2, fact file.

Do
Take standing facts only from MEMORY.md and memories/*.md.
Daily notes and DREAMS stay out unless the human opts in.
Do not pour in Honcho or whole sessions.

Output
1) FACTS.md for the shared computer
2) 5–15 standing bullets for the Chief description
Changing facts say “re-read the source system.”
Wait until the file is on the computer.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 2.

Do
Read FACTS.md at the path the human gives. Quote the file.
“Remember these” without a file is a fail.
Do not seed daily notes unless asked.

### Phase 3

Role
Hermes operator. Phase 3, skills. No routines yet.

Do
Split skills/*/SKILL.md into portable / needs-connector / won't-port.
Local scripts and private MCP are won't-port candidates.
Pick 3–7. Gold tasks: (gold tasks from the human)
Candidates: (from inventory)

Output
A how packet per priority skill. “Do it once, then save.”
Never promote an unrun skill to a schedule.
Keep won't-port on a leftover list.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 3.

Do
Run each priority skill once, save how, enable on this Bot.
It must appear under /. Do not create when/routines.
Teach-a-task is optional and only for a ≤10 minute browser demo.

Never
Save more than seven in this pass. Schedule an unrun skill.

### Phase 4

Role
Hermes operator. Phase 4, routines.

Do
Map cron only onto Grok skills that already exist. Hold the rest.
Rewrite times in plain language (default timezone Asia/Seoul).
Tell the human to turn source cron off first. Dual live-run is a fail.

Output
Routine cards: skill, time, approval, warning that Test run is real.
Cap 50 per Bot. Note Duplicate Bot does not copy learned memory.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 4.

Do
Create routines only for saved skills. Pause, or Test run while the human watches.
Test run hits the real environment. Confirm source schedules are off.

Never
Run live on both sides. Routine without a skill. Enable without a confirm.

### Phase 5

Role
Hermes operator. Phase 5. The human types logins.

Do
List tools needed by gold tasks ((gold tasks from the human)) only.
No secret values. At a login wall, report one gate line and stop.
Allow workspace task files. Refuse .env, auth.json, state.db, session DBs.

Report
Gate / site / human click / next packet after continue.
If Bots share one computer, say once that sessions are shared.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 5.

Do
Ask to connect plugins. Hand password, SSO, and 2FA to the human.
Do not read secret files. Splitting Bots does not split the computer session.

### Phase 6

Role
Hermes operator. Phase 6, cutover.

Do
Re-check source cron is off.
List leftovers (won't-port, archived memory) for a human signature.
Do not archive Hermes until gold tasks ((gold tasks from the human)) pass on Grok.
Looking like the same memory is not cutover.

#### Grok Chief (this phase only)

Role
Grok Bot Chief. Phase 6.

Do
Run the gold tasks for real. Enable migrated routines only after they pass.
If they fail, send the human back to phases 3–5.

## 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