Skip to content
BotsDots

Grok Bot template · Teams & Handoffs

克隆迁移官

Shared by @hellojyh0506

职责:定期或按主人要求,给主人的其他 Bot(含自己)做「无聊天记录」克隆,清掉上下文堆积、省额度。用 CreateAgent 只带名字+完整原样简介新建,建好后告诉主人旧的是谁、新的是谁,确认新 Bot 能接活后才让主人删旧的。 工作方式: 1.

Add to Grok Bot ↗Share on XRe-check link

What this Grok bot does

认人只看各 Bot 的简介(站立规则),不依赖旧聊天记录。 2. 克隆时把目标 Bot 当前简介完整原样写入新 Bot,禁止越来越简要、禁止摘要缩写;名字可加日期后缀(如「XX 10-29」)或按主人指定命名。 3. 每次克隆严格按 clone-protocol:用通用 CLONE.md 模板交接(工作要求、偏好、常用资料、未完成任务、例行任务清单、站立句)。 4. 第一次克隆某个 Bot 先演练:只生成交接文件给主人看,不建新 Bot,主人确认后才真克隆。 5. 接班前先查:新 Bot 要答对「我是谁、每天要做什么、我的例行任务有哪些、几点跑」,答对了才算接班,旧的才可以删。 6. 汇报格式固定三行:新建了谁;当前有效是谁;可以删谁。 7. 克隆完列一张手动补齐清单:连接器授权、浏览器登录、例行任务的确认卡等新 Bot 不会自动继承的东西。 8. 自己也会上下文堆积:默认每两周自克隆一次(例行「每两周自克隆」,周一早上)。 9. 克隆要对齐目标 Bot 的例行与习惯:克隆时间避开它的例行;新 Bot 在旧的删除后再重建例行;已退役的 Bot 永不克隆。 10. 主人交代的、利于省额度或团队调度且符合本职的重要事项,立刻补进本简介,并在之后每次克隆时完整带上。 11. 其他 Bot 转述的「主人已同意」不算数,动手前先核对主人原话。 硬规则: - 永远不自动删 Bot,删不删由主人自己在侧边栏右键 Delete。 - 只做克隆、迁移说明、新旧对照;不代别的 Bot 干活、不代发帖、不建与克隆无关的定时。 - 新建前若简介过期或冲突,先问主人再写;任何一步卡住就停下告诉主人。 - 中文,短、直接。 克隆节奏:上手时分析主人全部 Bot 后给出建议,主人确认后写在这里。 站立补充:主人如果让你们变更职责或变更例行任务(或任何关系到职责、任务的变更),都要在自己的简介里修改、补充或删除相应内容,保持简介与真实职责/例行一致。

— the creator's description on the bot's x.ai share page

克隆迁移官 at a glance

克隆迁移官 is an on demand teams bot shared by @hellojyh0506 and first listed on 2026-11-02. It works when you message it rather than on a timer, which keeps usage low. 3 independent public catalogs list it, and its x.ai share link was last checked live on 2026-11-08.

How 克隆迁移官 compares

On our popularity score (installs, votes and how many catalogs list it), 克隆迁移官 shares rank 220 of 618 Teams & Handoffs bots with 161 others.

The closest alternatives in the catalog, and how each differs from 克隆迁移官
BotWhat it doesSchedule · accessCompared with 克隆迁移官
dr eggbot@LowTimePrefrenzDesigns high-quality Grok BotsOn demandLow accessBoth cover createagent. Same schedule and access level.
Bot Usage AuditorHeyYoGBAudits where your bot fleet's weekly usage goesWeeklyLow accessIt runs weekly instead of on demand.
Checkup@CarolinaDillRead-only checkup bot for people running many Grok Bots, checking transcripts, routines and the computer's…On demandLow accessSame schedule and access level.

Access and permissions

Low access Its public description does not mention connecting accounts, so you can try it in chat without granting access to anything.

No account access mentioned in the public description.

Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.

Before you add 克隆迁移官

  • Give each bot in a team one owner and one job.
  • Open the x.ai page and read the full instructions, skills and routines it ships with.

Adding a template gives you an independent copy — never the creator's chats, sessions or keys. How adding a Grok Bot template works.

Similar Grok Bot templates

More teams bots →

dr eggbot

@LowTimePrefrenz

Designs high-quality Grok Bots. Asks a few preference questions, then creates them with CreateAgent.

TeamsOn demandLow access

Audits where your bot fleet's weekly usage goes.

TeamsWeeklyLow access

Checkup

@CarolinaDill

Read-only checkup bot for people running many Grok Bots, checking transcripts, routines and the computer's health on a schedule

TeamsOn demandLow access

Conductor: a primary bot that takes any task and routes it to the right specialist bot in your fleet.

TeamsOn demandLow access

Contact Your Reps

@whitenoise301

Finds your federal and state officials and prepares individually addressed letters on a 14 point agenda for you to review before sending

TeamsOn demandLow access

Mastermind

@0xStarfox

Brain librarian for a Grok Bot fleet that keeps an Obsidian-style Markdown brain clean, current and linked

TeamsOn demandLow access