Move an old AI agent folder into Grok Bot

How this helps you

You keep what worked in your old setup without rebuilding everything by hand.

✦ Try it

Here is my old AI agent setup: [folder or repo]. Go through it one role at a time with me. For each agent, propose: keep as its own Bot, merge into another, or turn into a shared skill. For every Bot you propose, give its one-sentence job and what it must never do. Don't create anything until I approve each one.

Fill in: [folder or repo] is where your old agent files live, for example a zipped folder you upload or a GitHub repo.

What they did

Tom from ICOR ran his whole business and life from a local folder of 59 agents, each with its own instruction file and journal, plus 149 procedures and dozens of work streams. The rules started to fight each other. He moved it into Grok Bot by talking it through with his lead Bot one role at a time: who stays, who merges, what goes into a Bot's instructions and what becomes a skill every Bot can use. He did much of it by voice while driving. He ended with about two dozen Bots, 21 shared skills, three routines and eight group chats, which replaced his work stream files. His advice: start small, write down what each Bot must never do, and if you can't say in one sentence what a Bot does, it shouldn't exist.

Who it's for: People coming from Claude Code, Codex or other agent setups with lots of instruction files.

Before you start

An existing agent setup: a folder of agent or instruction files, skills or procedures.
A way to give your Bot those files (upload, a connected drive, or a Git repo).

How to try it

Give your lead Bot access to the old folder.
Paste the prompt below and go through it one role at a time.
For each old agent, decide: keep as a Bot, merge into another, or turn into a shared skill.
Write each Bot's one-sentence job and its never-do list into its instructions.
Replace work stream files with group chats for jobs that need several Bots.
Add routines last, only for jobs that already work by hand.

What to expect

Tom went from 59 agents to about two dozen Bots, with descriptive names such as finance and health, and his lead Bot still the first contact.

Common mistakes

Copying every old agent over one to one. Merge the ones that always work together.
Bringing every procedure across. Tom's lesson is that too many rules start to contradict each other.
Skipping the never-do list, which he says matters more than you think.

Related tips

One job per Bot: Give each Bot one job and a list of things it never does.
Keep lasting rules in the description, not memory: Duplicate a Bot and the description comes along; memory starts empty.
Keep skills in a GitHub repo and sync them to your Bots nightly: One-line routines call skills; the skills live in a repo you edit elsewhere, and a nightly routine pulls them onto the Bots' computer.
Run Claude Code or Codex on your Bot's computer with your own plan: Your Bot's computer has a terminal, so it can install a coding CLI, you sign in once, and your Bots can use that subscription from anywhere.