全部使用案例

工作

让主 Bot 读完官方指南,给你的 Bot 团队提“家规”

官方指南里好做法很多,但没人有空逐条对照自己的配置。

分享

当时卡在哪

Ben Lang(@benln)建议大家让主 Bot 去读新的指南并推荐最佳实践;Victor Kryukov(@vkryukov)照做了,并公开了他的 Bot 按价值排序的八条做法,每条都对应到他自己的配置。与 xAI 无关。

要装什么、建什么

让主 Bot 读完指南,按价值从高到低列出值得你的 Bot 采用的做法,并给出具体提案。他的清单第一条是 Auto-review 规则(没有你同意不买东西、不预订,不在它自己电脑以外删除东西),接着是把纠正变成规则、每周自检、例程默认安静、编码 PR 必须附证据。

机器人

  • Main bot

    读官方指南,按你的配置排出值得采用的做法。

插件

  • 第一天不用插件。按「第一次怎么跑」做。

例行任务

  • 第一次先别开。自己看过一轮再说。

提示词

从指南中排出的做法(作者原文)

引自 @vkryukov — 按其公开原文。不要另编系统提示词。

(作者英文原文)I read all 15 Grok Bot guides. These are the practices worth adopting, most valuable first:

1. Write Auto-review rules. The guides warn that a login one bot uses works for every bot. Our shared 1Password vault has no stated limits. Proposed rules: no purchase or booking without your OK unless a routine you approved does it, and no deletes outside my computer. They'd go in Auto-review rules.
2. Turn every correction into a rule. When you correct a bot, it writes the rule into its skill or memory right away. Improver would review real mistakes and tell the other bots about the fix.
3. Run a weekly self-audit. Improver would ask which routines fire but get ignored, what you've requested by hand three times, and what should exist but doesn't. Each answer becomes a yes or no for you. The X watch would also track what it already covered, so it reports only new tips.
4. Use your voice in emails you send. Build a style profile from your sent mail, then learn from how you edit my drafts before you press Send.
5. Watch for dropped promises and unanswered asks. Inbox Triage flags emails you sent that never got a reply, and promises you made, only when the next move is yours. It goes into the morning brief.
6. Default routines to quiet. If nothing changed, send nothing. Specialists report through me unless it's urgent. New routines start paused with a sample run until you turn them on.
7. Verify before claiming. Add standing rules to shared memory. Open the live thread before stating anything. Treat an empty search as unverified. Preview family calendar and Basecamp changes before saving them.
8. Require proof in coding PRs. Builder attaches test output and before and after screenshots. It fixes failing checks and merge conflicts before asking you to merge.

第一次怎么跑

  1. 1阅读 https://x.com/vkryukov/status/2107501842741752047(致谢 @vkryukov)。
  2. 2对主 Bot 说:读完官方 Grok Bot 指南,为我的 Bot 推荐最佳实践,按价值排序,每条对应到我的配置。
  3. 3把它的清单和下方他的八条对照;用不上的让它删掉。
  4. 4先批准一两条(Auto-review 规则和“例程默认安静”是不错的起点)。
  5. 5只让它落地这几条,展示改了什么,其余的以后再说。

审批围栏

这份清单只是提案,每条规则由你亲自批准;排第一的那条,正是为了让购买、预订和删除永远等你点头。

你该改什么

别自己啃手册——让 Bot 对照你的配置去读,再把一条条“要/不要”的提案交给你。

出处

Victor Kryukov @vkryukov · 原帖

与 xAI 无关。提示词不是我们写的。第三方模板条款照旧适用。

去看模板

去看团队蓝图

Pro 设置包

想要完整设置,而不只是思路?

Pro 设置包为热门用例提供岗位描述、提示词、排程与踩坑。

了解 Pro