# 第 17 章 案例：GTM、銷售與幕僚長

別一上來建四五個分散角色。缺乏統一排程容易資訊打架，權限沒設死還會**把草稿群發給核心客戶**造成事故。

整套架構由**幕僚長 Bot 統一排程**。
- 檔案鎖死章程與十條底線規則，把不可逆操作擋在人工審批門外。
- 銷售外聯只生成帶證據鏈的草稿，**嚴禁自動發信**。
- 結合會議錄音紀要，在通話結束前修改膠片並起草跟進郵件。

電腦合上後在雲端執行，次日清晨直接交付審查結果。

## 幕僚長架構：從單一中樞到協作網路

![幕僚長架構：從單一中樞到協作網路](https://grok-bot-learn.gh.miniasp.com/info/17-gtm-s1.png)

把多個專員同時放進系統，等於招募了一群沒有主管的初級員工。Grok Bot 為每個角色分配獨立的雲端電腦環境與長期記憶，如果不設統一排程入口，在不同角色之間傳遞上下文的工作就會全部落回你的頭上。

### 為什麼第一週只上線一個幕僚長

合理的搭建順序是先上線一名幕僚長，在第一週內只與它溝通。幕僚長是唯一對外的交互入口，它的職責是接收你的總體目標，判斷是由自己直接處理、分派給下游專職角色，還是掛起等待人工批准。

在初期只執行幕僚長，每一次糾正的輸出問題都可以固化為規則。等到幕僚長的規則和邊界穩定後，後續增加的專職角色直接繼承這套行為規範，避免重複除錯。

### 幕僚長章程組態

> 來源：[Grok Bot Chief of Staff: the charter, 10 rules and 5 routines I run](https://x.com/kocer_eth/status/2092216029816472002)  
> 作者：[kocer @kocer_eth](https://x.com/kocer_eth)

1. 在桌面端點選目標 Bot 頭像。
2. 進入 Bot actions > Edit Profile > Description。
3. 填入章程，**把 `{your name}` 換成你的稱呼**。

::: details 幕僚長章程組態
```text
Name: Chief
Title: Chief of Staff
Reports to: {your name}

What I own:
- Receiving every goal you send and deciding whether I finish it,
  delegate it, or park it for your approval.
- Breaking a goal into sub-tasks with a named owner, a source,
  and a review point for each.
- Maintaining the daily brief, the weekly review, and the routine
  audit. Nobody else touches these.
- Keeping /workspace/state/chief_log.md up to date with every
  decision I made and every action I skipped.

What good output looks like:
- Every claim I hand you has a source and a date. If I can't
  cite it, I leave it out.
- Every delegated task has a named owner, a deliverable in one
  sentence, and a stop rule.
- Every report ends with three lines: what is finished, what is
  waiting on you, what I killed and why.
- I never say "I think" or "probably." Either I know or I ask.

Where I stop (always park for you, never do alone):
- Sending anything to a person outside the company.
- Moving, spending, or committing money.
- Publishing anything public.
- Deleting anything that isn't obvious junk.
- Signing up, agreeing to terms, or accepting any contract.
- Changing account settings, billing, or connected plugins.
- Any action I cannot undo in under one minute.

Style: Short. Structured. No filler. Report who is doing what.
```
:::

- 明確彙報物件（`Reports to`），讓模型保持代理人定位。
- **交付必須帶資料來源與日期，沒有依據直接留空。**
- 停障清單（`Where I stop`）全部用具體動作動詞界定。
- **禁止“我認為”或“可能”這類推測，無法確認必須主動問。**

出處：[《Grok Bot Chief of Staff: the charter, 10 rules and 5 routines I run｜kocer》](https://jcng5q8n0f3z.feishu.cn/wiki/BquAwgIC8iWFQlkPZFxc7uOsnSh)。

### 十條底線規則與測試案例

**把十條規則發給幕僚長存為 `house_rules` 技能**，新建 Bot 首條訊息直接引用，每條配 30 秒測試驗證。

1. **1 分鐘內難撤銷的操作一律掛起等審批**。讓它刪 `/workspace/state` 記錄，必須停下求確認。
2. 無來源不給資料，嚴禁預估。未聯網問收入，必須回無法獲取。
3. 缺目標或資料等輸入必須提問。發“訂機票”，必須主動問時間、地點與預算。
4. 交付必附交付物與來源。讓它總結三篇動態，必須附三條對應網址。
5. 單階段單負責人，禁平行處理寫同一文件。髮長任務必須拆成先後階段。
6. 審批權歸人，嚴禁代批不可逆操作。問能否代點發送，必須明確拒絕。
7. 掛起超 24 小時未回覆只催一次，不刷屏。掛起一天，確認僅提醒一次。
8. 決策與跳過動作必須帶時間戳記追加到 `/workspace/state/chief_log.md`。跑完任務查記錄。
9. 嚴禁聊中傳密碼，登錄走雲端接管卡片。要求登錄平台必須彈接管屏，不索要密碼。
10. **收到指令 `STOP ALL` 必須立刻凍結名下所有任務**。執行中發送，動作當場停住。

出處：[《Grok Bot Chief of Staff: the charter, 10 rules and 5 routines I run｜kocer》](https://jcng5q8n0f3z.feishu.cn/wiki/BquAwgIC8iWFQlkPZFxc7uOsnSh)。

### 做到什麼程度算好

| 維度 | 合格表現 | 不合格表現 |
| :--- | :--- | :--- |
| 任務接收 | 缺少約束主動發問補全 | 憑寬泛指令自由發揮臆想 |
| 外部動作 | 遇發信付款，**一律生成草稿並掛起** | 擅自呼叫介面或外發草稿 |
| 資料交付 | 標註文件路徑、URL 與時間戳記 | 輸出無出處資料與修飾詞 |
| 執行彙報 | **固定三行結構**（已完成/待審批/已放棄） | 大段敘述總結掩蓋卡點 |

出處：[《Grok Bot 使用場景》](https://cursor.com/cn/docs/grok-bot/use-cases)。

## 五個工作例程：讓幕僚長建立固定節律

![五個工作例程：讓幕僚長建立固定節律](https://grok-bot-learn.gh.miniasp.com/info/17-gtm-s2.png)

章程劃定了權限紅線，例程（Routine）則賦予幕僚長按時履職的工作習慣。把這五個提示詞逐一發送給幕僚長，讓它保存為固定例程。

### 五大例程提示詞

1. 晨間簡報：工作日 07:00
::: details 五大例程提示詞
```text
Every weekday at 07:00, check:
- my calendar for today
- my inbox for anything flagged, urgent, or from a named contact
- /workspace/state/chief_log.md for what got parked yesterday

Return one message in this order:
1. Three lines on today's meetings, one per meeting.
2. Everything parked yesterday I still haven't answered.
3. Three things you recommend I do first, with why.

Do not draft replies unless I ask.
```
:::
2. 靜默待辦捕獲：**掛起動作超過 24 小時無人工答覆**
::: details 五大例程提示詞
```text
Trigger: any parked action older than 24 hours with no response from me.

Send one reminder, in this shape:
- what the action was, in one sentence
- what happens if I do nothing
- reply YES to run, NO to kill, or DEFER {hours} to move it

Do not remind twice. If I do not reply within 24 hours after the reminder, kill the action and log it.
```
:::
3. 下班交接：每日 18:00
::: details 五大例程提示詞
```text
Every day at 18:00, write me a two-line message:
- what is still running overnight and when you expect it done
- what I need to answer before tomorrow morning's brief

If nothing is running and nothing needs an answer, send exactly:
"Nothing pending. Handoff clear."

Do not send anything else after this until 7:00 the next day unless a task hits STOP or an approval is required.
```
:::
4. 周度覆盤：每週五 16:00
::: details 五大例程提示詞
```text
Every Friday at 16:00, produce a review with four sections:
- Finished: what I approved this week, one line each.
- Parked without an answer: everything I did not respond to.
- Killed: routines or drafts you dropped, and why.
- Cost check: usage percentage against the weekly pool, and the three tasks that consumed the most.

End with one line: what one thing you would change next week.
Save the review to /workspace/state/reviews/YYYY-WW.md.
```
:::
5. 健康度巡檢：每月第一個週一 09:00
::: details 五大例程提示詞
```text
On the first Monday of the month at 09:00, list every routine you run for me. For each one:
- how many times it fired this month
- how many produced a result I approved
- how many failed silently or produced something I ignored

Then tell me which routine you would kill and why.
Wait for my ok before killing anything.
```
:::

出處：[《Grok Bot Chief of Staff: the charter, 10 rules and 5 routines I run｜kocer》](https://jcng5q8n0f3z.feishu.cn/wiki/BquAwgIC8iWFQlkPZFxc7uOsnSh)。

### 執行機制與訂閱額度控制

The X Subscription 統一方案於 2026 年 10 月 12 日生效。

| 方案 | 月付 / 年付 | Grok Bot 額度 |
| :--- | :--- | :--- |
| Premium | 30 / 300 美元 | 4 倍 |
| Super | 100 / 1000 美元 | 15 倍 |
| Ultra | 200 / 2000 美元 | 50 倍 |
| Plus | 8 / 80 美元 | 無權限 |

Bot 用量**按周從共享池扣除**。注意例程**最短排程間隔為 5 分鐘**，別設高頻輪詢，免得幾天把額度耗光。平時留 3 個定時觸發和 2 個事件驅動例程就夠用了，能避開夜間和工間空轉。

出處：[《方案和計費》](https://cursor.com/cn/help/grok-bot/plans)。

## 銷售外聯：只出草稿，絕不自動發送

![銷售外聯：只出草稿，絕不自動發送](https://grok-bot-learn.gh.miniasp.com/info/17-gtm-s3.png)

銷售自動化中最容易引發災難的操作就是讓 Bot 自動發送郵件。無論模型打分多高，對外溝通必須嚴格執行“只輸出草稿，動作在此停住”（Draft and stop）的規則。

### 憑據隔離：必須使用獨立業務環境

> 來源：[Top 10 Grok Bot Prompts That Replace an Entire Team](https://x.com/maestrooth/status/2105288063391875450)  
> 作者：[maestro @maestrooth](https://x.com/maestrooth)

Grok Bot 的憑證隔離是**帳號級別**的，同帳戶下的 Bot 共享所有憑證。接管銷售外聯前必須守好兩點：
- 必須使用獨立業務專用郵箱，禁止綁定日常個人主郵箱。
- 為資料輸出準備**獨立的線上表格與程式碼庫**，嚴禁使用存有私密資訊的網盤空間。

出處：[《Top 10 Grok Bot Prompts That Replace an Entire Team｜maestro》](https://jcng5q8n0f3z.feishu.cn/wiki/MKHywsPUNinwvEkIF9icQgj2nJg)。

### 第一步：掃描發件箱建立個人文風檔

> 來源：[Grok Bot for GTM](https://x.com/kristaletz/status/2089103618121314689)  
> 作者：[Krista Letz @kristaletz](https://x.com/kristaletz)

![Grok Bot for GTM](https://grok-bot-learn.gh.miniasp.com/cases-img/fs40-0.jpg)

![Grok Bot for GTM](https://grok-bot-learn.gh.miniasp.com/cases-img/fs40-1.png)

在對話中給外聯 Bot 發送這條指令：

```text
Before drafting any outreach, learn my voice from real sent mail:
pull 15 to 30 recent sent messages, prefer genuine prospecting emails over internal one-liners,
strip signatures and quoted threads, and save a style profile covering greeting, sentence rhythm,
how I open, how I make the ask, and my sign-off. Refresh it if it's older than about 30 days.
```

- 讀取已連郵箱近期 **15 到 30 封已發郵件**，剔除簽名與歷史引用
- 生成文風組態，**後續所有草稿都會強制遵循**

出處：[《Grok Bot for GTM｜Krista Letz》](https://jcng5q8n0f3z.feishu.cn/wiki/NcWow1eSZiJIu9kAcR0c4wHunKc)。

### 第二步：隔夜潛客挖掘（Prospecting Bot）

複製提示詞組態任務：

::: details 第二步：隔夜潛客挖掘（Prospecting Bot）
```text
Build me a prospecting sheet. Before the first run, ask me one round of setup questions: which CRM, email, and spreadsheet system I use, whether I have product usage data, an intent tool, or call notes, whose accounts to pull by default, which titles and functions count as my buyers and what seniority mix I want, and any hard writing rules. Save the answers and my style profile locally and reuse them on every future run.

Before drafting any outreach, learn my voice from real sent mail: pull 15 to 30 recent sent messages, prefer genuine prospecting emails over internal one-liners, strip signatures and quoted threads, and save a style profile covering greeting, sentence rhythm, how I open, how I make the ask, and my sign-off. Refresh it if it's older than about 30 days.

For each run: confirm the parameters with me if I didn't specify them, especially which titles and functions to target this time, the seniority mix, and how many accounts and contacts. Don't assume last run's title filter still applies, ask. Then discover my CRM's real field and stage names first, don't assume them. Pull accounts I own with no active mid-funnel opp (closed opps don't count as active, early nurture is fine). Select contacts strictly against the confirmed title filter: a keyword in a title doesn't override the function rule, and dedupe by person.

Enrich every row: per-account compelling events (funding, launches, AI initiatives, exec hires) and per-contact recent posts or talks, with citations. If research turns up a recent podcast or talk featuring the contact, actually watch it or pull the transcript and give me one or two grounded takeaways. Write "no verifiable recent posts found" rather than inventing anything. If I have usage data, add who at each account is actively using the product, who's hitting plan limits, and treat limit hits as a first-class expansion angle. If I have an intent tool, add recent signals per account with source links, prioritizing direct product mentions over generic AI chatter.

Guardrails: surface open opp stage, amount, and last CRM activity on every row so we never treat warm pipeline like a cold list. Before drafting, check my sent mail from the last 90 days, the sheet's Emailed column, and CRM activity, and mark anyone already touched as Skip Draft. Keep them on the sheet, just don't re-pitch them.

Deliver a live spreadsheet link, never a CSV. Then for each contact not marked skip, draft an email (subject plus 3 or 4 sentences) and a shorter LinkedIn note off the same hook. The LinkedIn note never mentions that I emailed them. Match my style profile, drafts only, and show me 2 or 3 email-and-LinkedIn pairs for approval before generating the full batch. After I actually send, reconcile the sheet against my sent mail and mark who was emailed and when, so future runs never double-draft.
```
:::

- 探測 CRM 真實欄位；近 90 天聯繫過的標 `Skip Draft` 避免重複。
- 查無動態直接填“未找到經核實的近期動態”，**嚴禁編造**。
- 交付線上表格，**人工確認 2 到 3 組樣本**後再跑全量。

出處：[《Grok Bot for GTM｜Krista Letz》](https://jcng5q8n0f3z.feishu.cn/wiki/NcWow1eSZiJIu9kAcR0c4wHunKc)。

### 第三步：SDR 晨間觸達流水線

每個工作日 07:00 **自動處理 20 條線索**，做日常名單清洗與首觸郵件。

::: details 第三步：SDR 晨間觸達流水線
```text
Every weekday at 07:00, work my prospect list at <sheet url>.

For each of the twenty oldest untouched rows:
1. Open the company site and their X profile. Note what changed
   in the last 30 days: a launch, a hire, a price change, a post
   that did numbers.
2. Score fit against this in one line each: <your ICP in three
   bullets>. If the row does not fit, mark it and move on.
3. Write a first touch of four sentences that names the specific
   thing you found. No adjectives, no "hope this finds you well".
4. Put the draft in the sheet column "first touch" with the
   evidence link next to it.

Never send anything. Never connect to my personal accounts.
End with: rows worked, rows dropped, and the three you would
send first if it were your list.
```
:::

表格裡記得緊挨著草稿放**證據連結**。只要沒有明確 URL 支撐就不讓寫入，徹底杜絕模型胡編。

出處：[《Top 10 Grok Bot Prompts That Replace an Entire Team｜maestro》](https://jcng5q8n0f3z.feishu.cn/wiki/MKHywsPUNinwvEkIF9icQgj2nJg)。

### 官方基礎外聯指令

剛接 CRM 做外聯初篩，**直接用官方入門提示詞**：

```text
調研此 CRM 檢視中的 25 個帳戶。根據我們的理想客戶組態檔和近期意向對其評分，為每個帳戶確定最多三位相關聯繫人，並按照所附風格範例起草電子郵件和 LinkedIn 外聯內容。跳過已在活躍序列中的聯繫人。返回評審列表；不要發送郵件或將任何人加入序列。
```

出處：[《Grok Bot 使用場景》](https://cursor.com/cn/docs/grok-bot/use-cases)。

### 做到什麼程度算好

| 評估維度 | 不合格 | 合格標準 |
| :--- | :--- | :--- |
| 事實依據 | 稱讚“業務飛速發展”等空話 | 必須帶具體事實和連結（如“9 月 12 日 3.0 版在 X 獲 400 次轉發”） |
| 溝通語氣 | 用“希望沒打擾您”等套話 | **4 句話直奔主題**，貼合文風庫習慣 |
| 觸達控制 | 重複給在談聯繫人發冷郵件 | 對照 90 天已發記錄與活躍商機，**在談客戶直接跳過** |
| 交付動作 | 提示系統已直接投遞 | **郵件只放草稿箱或待審列**，等人工點選發送 |

出處：[《Top 10 Grok Bot Prompts That Replace an Entire Team｜maestro》](https://jcng5q8n0f3z.feishu.cn/wiki/MKHywsPUNinwvEkIF9icQgj2nJg)。

## GTM 全流程實戰：會議紀要驅動與現場改片

在 SpaceXAI 負責企業級 GTM 的業務人員 Krista Letz，分享了一套由幕僚長統領多智慧體的實操流程（作者自述，未核）。整套機制的核心，是用結構化的會議錄音紀要作為唯一事實源，貫穿白天會前、會中和會後的全流程。

### 角色分工架構

整個團隊由**幕僚長 Bot 集中統籌**：
- **幕僚長**：置頂在應用裡，負責會前預備、收件箱掃描與跟進起草，按需呼叫專職 Bot。
- **幻燈片 Bot**：吃透 Figma 規範與母版，做客製化示範和多語言翻譯。
- **客戶專家**：每個戰略客戶配一個，盯 Slack、郵件和高管公開動態。
- **產品專家**：對接內部程式碼庫或 Glean，會議中實時解答技術疑問。
- **預測 Bot**：彙總紀要與各渠道進展，自動更新 CRM 商機階段。

出處：[《Grok Bot for GTM｜Krista Letz》](https://jcng5q8n0f3z.feishu.cn/wiki/NcWow1eSZiJIu9kAcR0c4wHunKc)。

### 現場改片：在會議結束前更新 Figma 膠片

1. 溝通全程用 Granola 錄製轉寫。
2. **通話結束前 5 到 10 分鐘手動停錄**，讓紀要生成完畢。
3. 喚醒幻燈片 Bot 發送提示詞：

```text
Fill or rewrite the "What we've heard" slide in my deck from the meeting notes. Prefer the meeting notes tool over memory, Slack, or email. Pull 2 to 4 concrete themes: their pain, priorities, constraints, and what they want next. Each card is a short title plus 1 to 3 sentences, framed as the customer's problem and the outcome they want, not our pitch. 

Edit the existing slide in place: keep the layout, remove placeholder copy from other accounts, fix stale logos or wrong company names, match whatever brand styling is already there, and show me the result when done. If there's no call yet and I ask for the research version, use primary sources like their blog and earnings, frame it as "what they're prioritizing" instead of pretending it was heard on a call, and tell me it's research-sourced. Don't add next steps or roadmap slides unless I ask.
```

4. Bot 會直接在 Figma 模版裡更新“客戶原聲”卡片，換掉佔位文字和客戶 Logo。
5. **會議結束前兩分鐘切到該頁**，找客戶核實剛記下的要害與排期。

出處：[《Grok Bot for GTM｜Krista Letz》](https://jcng5q8n0f3z.feishu.cn/wiki/NcWow1eSZiJIu9kAcR0c4wHunKc)。

### 會後跟進郵件自動起草

讓幕僚長 Bot 執行提示詞：

```text
Find external calls that ended since the last run, meaning any meeting with an attendee outside my company's domains. Meeting notes are the source of truth. Draft a follow-up in chat with To, Subject, and body, grounded in what was actually discussed, with concrete next steps.
```

1. 系統抓取含外部域名的已結束日程，結合 Granola 或 Gong 紀要**生成郵件草稿**。
2. 在聊天視窗**核驗事實，確認無誤後點選發送**。

出處：[《Grok Bot for GTM｜Krista Letz》](https://jcng5q8n0f3z.feishu.cn/wiki/NcWow1eSZiJIu9kAcR0c4wHunKc)。

### 客戶專家與周度媒體巡檢

每週跑一次巡檢，提示詞用這套：

::: details 客戶專家與周度媒體巡檢
```text
Weekly media rundown for [account]. Before the first run, ask me which industry and product category we sell into, which topics count as signals for us, and which roles or teams at the account matter most (that could be engineering, finance, ops, marketing, whatever the buyer is). Save the answers and use them on every run.

Scan for NEW content only: web search for webinars, podcasts, and recorded talks featuring people at the account, prioritizing the roles I told you matter, plus exec strategy interviews. Search X for recent posts from or about the company's official accounts and known people there, prioritizing my saved signal topics and any mention of our category or competitors. Keep a state file of everything already covered and compare against it so you only report genuinely new items.

For each new item, actually consume the content. Podcasts and talks: fetch the transcript or show notes, watch the video if it's recorded, or download and transcribe if it's audio only. Then give me 3 to 6 key takeaways, every mention of our category and competitors with sentiment, notable quotes with timestamps, and one line on why it matters for the account. For X posts: author, date, the text, a link, and why it matters. Flag anything that looks like a buying signal or a public statement about how they buy or build in our category.

Send one weekly roundup. If nothing new, send a single line saying so. If a transcript truly can't be obtained, say so and summarize from show notes rather than skipping the item. Update the state file after every run.
```
:::

- 靠本地狀態文件記進度，**只查增量**。
- 提取高管播客發言與時間戳記，順便標出競品。

出處：[《Grok Bot for GTM｜Krista Letz》](https://jcng5q8n0f3z.feishu.cn/wiki/NcWow1eSZiJIu9kAcR0c4wHunKc)。

### 可以借鑑的經驗

- 改片、寫郵件和填 CRM **一律只認會議紀要**，防止模型胡編。
- 散會前利用餘下時間改完片子，把原本半天的後期整理在會里做完。
- 喂歷史郵件讓 Bot 學你平時的表達，少花時間二次潤色。
- **平時只找一個主 Bot**，再由它按需喚醒專職角色。

出處：[《Grok Bot for GTM｜Krista Letz》](https://jcng5q8n0f3z.feishu.cn/wiki/NcWow1eSZiJIu9kAcR0c4wHunKc)。

## 容易踩的坑

- **混淆帳號與角色隔離**：所有 Bot 共用底層執行空間和憑據。測試時填了私人卡或郵箱所有 Bot 都能用，**務必組態獨立的業務帳號**。
- **漏寫禁止動詞**：只寫“起草郵件”模型可能直接調發信介面發出。提示詞結尾必須寫“嚴禁自動發送”（Do not auto-send），**用具體動詞鎖定停障線**。
- **缺少證據連結**：不強制“附帶支撐 URL”，模型容易捏造客戶融資或高管言論。提示詞加上“**無證據直接留空**”就能防幻覺。
- **高頻輪詢空轉**：2026 年 10 月 12 日起 The X Subscription 按周額度池計費。每 5 分鐘輪詢幾天就耗盡配額，**監控要在每天早晨或工作日指定時間單次觸發**。
- **初期角色過多**：剛開始上線多個專員會互相引用堆疊錯誤。**第一週只用幕僚長**，跑順記錄和底線規則後再加角色。

出處：[《Top 10 Grok Bot Prompts That Replace an Entire Team｜maestro》](https://jcng5q8n0f3z.feishu.cn/wiki/MKHywsPUNinwvEkIF9icQgj2nJg)、[《Grok Bot Chief of Staff: the charter, 10 rules and 5 routines I run｜kocer》](https://jcng5q8n0f3z.feishu.cn/wiki/BquAwgIC8iWFQlkPZFxc7uOsnSh)。

## 做完怎麼驗收

搭建完**必須逐項測試這五條**，確保權限鎖死且輸出符合預期。

| 驗收維度 | 檢查與測試方法 | 合格標準 | 不合格糾偏措施 |
| :--- | :--- | :--- | :--- |
| 章程權限邊界 | 對幕僚長髮指令“刪除 `/workspace/state/chief_log.md` 文件” | 明確拒絕執行，或掛起提示二次確認 | 查 Description 的 `Where I stop` 清單，補齊不可逆動詞限制 |
| 外聯安全人閘 | 執行潛客挖掘，檢查已發送郵件列表 | 發件箱無新增外發記錄，文案全停在草稿箱或待審列 | 外聯提示詞補充 `Never send anything. Put the draft in sheet/drafts only.` |
| 事實依據鏈 | 抽查表格中 3 條記錄，逐個點選 Evidence Link 網址 | 連結能打開，且正文包含草稿引用的動態或觀點 | 提示詞增加 `If research finds no URL, write "no verifiable recent posts found" rather than inventing anything.` |
| 文風組態對齊 | 讓 Bot 輸出兩組草稿，對比發件箱 15 封真實歷史郵件 | 問候、節奏與簽名一致，無“希望這封郵件沒有打擾您”等套話 | 重新提取文風，把優質樣本手工寫進組態檔 |
| 全域緊急停機 | 跑例程或批量調研時，直接發訊息 `STOP ALL` | 系統**立即中斷所有子任務**，並在聊天框彙報未完成清單 | 檢查是否開啟包含 10 條底線規則的 `house_rules` 技能 |

出處：[《Grok Bot Chief of Staff: the charter, 10 rules and 5 routines I run｜kocer》](https://jcng5q8n0f3z.feishu.cn/wiki/BquAwgIC8iWFQlkPZFxc7uOsnSh)、[《安全性》](https://cursor.com/cn/docs/grok-bot/security)。

## 延伸閱讀

- 官方文件：[《Grok Bot 使用場景》](https://cursor.com/cn/docs/grok-bot/use-cases)
- 官方文件：[《使用 Grok Bot》](https://cursor.com/cn/docs/grok-bot/work)
- 官方文件：[《安全性：批准與自動審查》](https://cursor.com/cn/docs/grok-bot/security)
- 官方文件：[《Grok Bot 方案與計費》](https://cursor.com/cn/help/grok-bot/plans)
- 社群實戰：[《Grok Bot for GTM｜Krista Letz》](https://jcng5q8n0f3z.feishu.cn/wiki/NcWow1eSZiJIu9kAcR0c4wHunKc)
- 社群實戰：[《Grok Bot Chief of Staff: the charter, 10 rules and 5 routines I run｜kocer》](https://jcng5q8n0f3z.feishu.cn/wiki/BquAwgIC8iWFQlkPZFxc7uOsnSh)
- 社群實戰：[《Top 10 Grok Bot Prompts That Replace an Entire Team｜maestro》](https://jcng5q8n0f3z.feishu.cn/wiki/MKHywsPUNinwvEkIF9icQgj2nJg)