import-bot-setup
use this on the first turn: hello, which tools, which workflows to make sure of, then run the whole import in order
Grok Bots DirectorySubmit a Grok BotLast checked Template updated
Brings your setup from Claude Cowork, Codex, ChatGPT, OpenClaw, and Hermes into Grok Bot, then creates the expert bots that cover it or adds to the bots you already have. Changes nothing in the old tools and scrubs secrets before anything is saved.
Nothing listed yet.
use this on the first turn: hello, which tools, which workflows to make sure of, then run the whole import in order
use this to pack the allowed files on the user's computer (macOS, Linux, or Windows) and copy the archive here, with fallbacks
use this for the account side: ranked fastest-first pulls of ChatGPT and Claude conversations, projects, and memories, with one sign-in at most and the official exports as the durable copy
use this to turn the archive and account pulls into inventory.json and sources.md with secrets scrubbed
use this after parsing: normalize every transcript into one shape, search across all sessions, and build each expert's history seed
use this after parsing when Cowork or Claude Code was found: stop the 30-day transcript cleanup, automatically on defaults, asking when the user set a value
use this to distill everything the old tools knew about the person into shared user memory, write it, show it, keep originals verbatim
use this to turn every project, task, skill, and recurring theme into the smallest set of expert bots that covers all of it
use this for every project that used a folder on the user's computer: copy it here, read it on request, or connect its drive
use this on every expert packet before spawning: title, card, instructions, skills, first conversation, routines, connectors, pre-spawn check
use this to write the packet file each expert saves from and the short pointer message it receives
use this to create every planned expert, hand each its packet, and give it its history skill
use this after spawning to lay out every routine across all experts, paused, and turn them on when the user picks
use this to map every connector the user relied on to a Grok Bot plugin, assign it to the expert that needs it, and make the case to connect
use this at the end: confirmed counts, who owns what now, routines to start with, connectors to connect, then clean up
use this on a later visit: bring over only what changed in the old tools, and fold in a late export or sign-in
use this when the user wants to rename, move a project, merge, split, or add to the experts after they were created
use this when there is little to import or a gap remains: six questions, then memory and experts from the answers
use this when local access is unavailable: send the user the collector for their system, then bring the archive here without local access
use this only as the source the copy command reads: import-tools.py, the Windows collector, and the Windows ChatGPT pull. Never read it into the conversation
Nothing listed yet.
Crafts multi-bot army sync with Notion as source of truth and Slack handoffs so you can reproduce your bot roster 1:1 across Grok Bot accounts — no personal da…
by Tim Salter
Builds purpose-driven multi-bot Grok Bot teams with a Team Expert, one Notion team hub, an owner channel for input, Notion Notes + Skills Loop. Goal/jobs drive…
by 🇲🇽
Holds the skill catalog for a team of Grok bots. You talk to the specialist; this bot routes work, remasters chats at 20 batches, and only searches for a new s…
by João
A bot designer for your Grok Bot team. It interviews you, creates focused bots with one job each, tunes their instructions, and runs light reviews so routines…
by Mike
Build and keep a private interactive org chart of your Grok Bot sidebar — sections, seats, Connections, zero-ellipsis names. Preview-first; quiet when staffing…