用 Operator Bot 与 Reviewer Bot 把重复工作固化成技能
一套 Grok Bot 工作流:一个 Bot 负责固定任务,把验证过的步骤存成技能,另一个 Bot 审核产出并标记缺失证据。

Stop making Grok Bot relearn a job you already taught it Stripe demonstrated the payoff: one integration task took roughly 20 engineering days with plain Claude Code and 4 with reusable prompts. Build that discipline into Grok Bot: 1. Give an Operator Bot one recurring job and a clear definition of done. 2. Save each proven step as a skill with inputs, validation checks, expected output and approval rules. 3. Give a Reviewer Bot the output, source links and run notes. Ask it to flag missing evidence, repeated investigations and failed tools. 4. Review its proposed skill edits, test them on a fresh example, then schedule the workflow. Private skills can be reused across your Bots. A routine decides when the work runs. For a competitor brief, let one Bot gather changes and another check every claim against its source. Measure correction count, review time and repeated tool failures to see whether the workflow is improving.
这条是引用着另一条写的:「Grok Bot 无人值守运维:权限与审批配置」