RT @Axel_bitblaze69: If you’re moving from Claude Code or Codex to Grok Bot, don’t dump your entire memory into one Bot..
you’ll end up with one confused agent carrying context it never needed..
i been stress testing Grok Bot for almost a week and i’m now moving my main workflow there with Cursor..
so i wrote a prompt that turns my current setup into separate context packs for each Bot..
one shared profile, one file per role, recurring routines, tool access and clear handoff rules.
it also leaves out every credential and private file.
paste this into Claude Code or Codex:
“Prepare my current setup for Grok Bot.
Inspect this project and my existing agent configuration files, including skills, memory files, CLAUDE.md, AGENTS.md, saved commands and workflow docs.
Do not read or include .env files, API keys, passwords, cookies, wallet data, private keys, seed phrases or session files.
Create a folder called grok-bot-migration containing:
1) shared-profile.md
My goals, preferences, writing style, business context and rules every Bot should know.
2) bot-roster.md
Suggest the smallest useful team of Bots based on my real workflows. Give each one a role, responsibility and clear boundary.
3) bots/
Create one markdown file per Bot containing its purpose, required context, recurring work, inputs, expected outputs, tools and when it should ask for approval.
4) routines/
Turn every recurring workflow into a separate file with its trigger, steps, frequency, success check and which Bot owns it.
5) skills/
Copy reusable skill files and remove duplicates. Do not rewrite instructions unless something is outdated or unclear.
6) tools.md
List the MCPs, connectors and tools I use, what each is for and which Bot needs it. Include names only, never credentials.
7) handoffs.md
Explain when Bots should message each other, what context they should pass and who owns the final result.
8) migration-checklist.md
Give me the exact order to create the Bots, add their context and test each workflow.
Do not modify or delete my original files.
Flag missing information instead of inventing it.
Keep shared context small. Put specialist information only inside the Bot that needs it.”
this should save me from rebuilding years of context one Bot at a time..
中文: RT @Axel_bitblaze69:如果你要从Claude Code或Codex迁移到Grok Bot,不要将整个内存丢弃到一个机器人中。
你最终会有一个困惑的代理人,它承载着它永远不需要的环境。
我一直在对Grok Boot进行压力测试,现在我正通过Cursor来推动我的主要工作流程。
因此,我编写了一个提示,将我当前的设置转换为每个机器人的独立上下文包。
一个共享配置文件,每个角色一个文件,循环程序,工具访问和清晰的交配规则。
它还会遗漏每个凭据和私密文件。
将此粘贴到克劳德代码或法典中:
为Grok Boot准备我的当前配置。
检查此项目以及我现有的代理配置文件,包括技能、内存文件、CLAUDE.md、AGENTS.md、保存的命令和工作流文档。
请勿读取或包含.env文件、API密钥、密码、Cookie、钱包数据、私钥、种子短语或会话文件。
创建一个名为 grok-bot-migration 的文件夹,其中包含:
1) 共享-profile.md
我的目标、偏好、写作风格、商业背景以及每个机器人都应该了解的规则。
2) bot-roster.md
根据我的真实工作流程,推荐最微小的实用机器人团队。给每个人一个角色、责任和明确的界限。
3)机器人/
为每个机器人创建一个标记下降文件,其中包含其目的、所需上下文、循环工作、输入、预期输出、工具,以及何时需要审批。
4) 日常习惯
将每个循环工作流程都变成一个独立的文件,并使用其触发器、步骤、频率、成功检查以及 Boot 拥有的文件。
5)技能/
复制可重用的技能文件并删除重复文件。除非内容过时或不明确,否则不要重写指令。
6) 工具。
列出我使用的 MCP、连接器和工具,每个工具的用途以及 Boot 需要哪些。仅包含姓名,绝不包含凭据。
7) 手接
说明机器人何时应该相互传递信息,应通过什么环境,以及最终结果的拥有者。
8) 迁移-检查列表
给我确切的顺序来创建机器人、添加上下文并测试每个工作流程。
请勿修改或删除我的原始文件。
标记缺失的信息,而不是发明它。
保持小而共享的语境。只将专业信息放入需要的机器人内部。
这应该会让我避免一次一次地重建多年的背景。