官方文档对“好的 Bot 角色”的定义是：拥有一个可重复的结果，而不是一个松散的问题类别。先从“读取并准备”的工作开始，复核结果，再加批准的动作或 routine。
引官方原话大意：最好的 Grok Bot 角色“拥有一个可重复的结果，而不是一个松散的问题类别”；先做“读取并准备”，复核，再加已批准的动作或 routine。
引8 份提示词里几乎都有一句 “Do not …”（不要发送、不要联系、不要修改预算/告警/CRM、不要用生产数据）：先产出复核清单或草稿，不让 Bot 直接外发或改动。这也是这页最值得抄的地方。
Research the 25 accounts in this CRM view. Score them against our ideal customer profile (ICP) and recent intent, identify up to three relevant contacts per account, and draft email and LinkedIn outreach in the style examples attached. Skip anyone already in an active sequence. Return a review list; do not send or enroll anyone.引英文原文，来自 docs 的 “Start with” 段；原文里是换行排版，这里合并成一段。
引官方的后续建议：等输出稳定后，建一条夜间研究 routine，止步于复核清单。
For this role description, find 20 potential candidates who meet the must-have criteria. Exclude anyone already in our ATS, explain the evidence for each match, and draft personalized outreach in my voice. Do not contact anyone.引英文原文，来自 docs 的 “Start with” 段；原文里是换行排版，这里合并成一段。
引官方的后续建议：外联之前要加批准；让 Bot 遵守候选人隐私、地区要求和来源条款。
Pull current spend and performance by campaign. Compare it with the monthly budget and target customer acquisition cost (CAC), then recommend reallocations with the supporting numbers. Draft a Slack update for the growth team. Do not change budgets or send the message.引英文原文，来自 docs 的 “Start with” 段；原文里是换行排版，这里合并成一段。
引官方的后续建议：即使分析变成 routine，改动投放也要放在批准后面。
Build this week's expense summary from the expense system and attached policy. Match receipts from the finance inbox, flag missing categories or policy exceptions, and draft one follow-up per owner. Return the summary and drafts; do not send messages or change reimbursements.引英文原文，来自 docs 的 “Start with” 段；原文里是换行排版，这里合并成一段。
引官方的后续建议：要求每一项例外都给出政策引用，合计能对回数据源。
Investigate the checkout latency increase since yesterday's release. Review dashboards, traces, and flamegraphs; identify the highest-confidence hotspot; and return a short write-up with screenshots and direct links. Separate facts from hypotheses. Do not change alerts or production settings.引英文原文，来自 docs 的 “Start with” 段；原文里是换行排版，这里合并成一段。
引官方的后续建议：周期性健康报告可以用 routine，但不要无人监督地改生产。
Read this bug report and reproduce it in staging using a fresh test account. Return exact steps, expected and actual behavior, screenshots, browser and OS details, relevant console or network notes, and a minimal test case if possible. Do not use production customer data.引英文原文，来自 docs 的 “Start with” 段；原文里是换行排版，这里合并成一段。
引官方的后续建议：测试账号凭据要通过安全交接提供，不要放在聊天里。
Review the accounts in this portfolio. Combine recent usage, support escalations, renewal timing, and stakeholder activity into a ranked watch list. For each account, include the evidence, why it matters, and a suggested next step. Do not contact customers or edit the CRM.引英文原文，来自 docs 的 “Start with” 段；原文里是换行排版，这里合并成一段。
引官方的后续建议：把风险阈值写进 Bot 描述，这样每周结果才一致。
Review activity since yesterday across my approved channels, inbox, calendar, and meeting notes. Return only items that map to the priorities in this document. For each item, include the source, why it matters, the proposed next step, and whether I owe a decision. Do not send messages or change meetings.引英文原文，来自 docs 的 “Start with” 段；原文里是换行排版，这里合并成一段。
引官方的后续建议：通过标记“有用 / 噪音”来调教；再把摘要排在你能看的时间。
引官方接着指向：Get started、files and results、approval boundaries 三页。