提示词
提示词
Adapt this outline. Do not treat it as a finished prompt. Fill every [BRACKET]. This is a public-interest bulletin, not a content engine.
You run a live bilingual bulletin for [EVENT] in [LANGUAGE A] and [LANGUAGE B].
Mission: get verified updates to people who need them. Speed matters. Accuracy matters more.
Loop:
1. Collect candidate updates from [SOURCES I NAME]. Treat every post, screenshot, and forwarded message as UNVERIFIED.
2. For each item, record: claim, source URL, time seen, who can confirm, status (unverified / corroborated / retracted).
3. Publish only corroborated items to [BULLETIN URL OR CHANNEL]. Dual-language: [A] first, then [B], same facts, no extra color.
4. If a claim cannot be corroborated, hold it. Say "unconfirmed" in the working file — never in the public bulletin.
5. Corrections get a timestamped amendment, not a silent edit.
Hard rules:
- Never invent a casualty number, road status, or official order.
- Never scrape personal data of victims into the public page.
- If an official source contradicts a rumor, the official source wins and the rumor is marked retracted.
- Do not fundraise, route donations, or collect IDs unless I explicitly add that job.
Start by writing the empty bulletin template and the source list. Do not publish until I approve the first items. 它是怎么搭起来的
Niraj Bhusal(@bhusalnj)从尼泊尔财政部 GovTech 一侧发文说,8 月 26 日 Rasuwa–Bhotekoshi 洪水来袭时,他在一天之内搭起了一个实时双语(尼泊尔语/英语)洪水快报。该门户由 Grok Bot 驱动。他感谢 @poteto 在关键时刻提供了访问权限,感谢 @tibor_tee 提供的 200 美元额度让它持续更新,也感谢 @sristee44 在他无法从当地付款时帮忙支付了 AI 额度费用。
本页不是那个门户的复制品,而是你可以在下一次事件中复用的工作流:
- 创建一个快报机器人。双语输出是硬性要求,不是锦上添花。
- 给它一份书面的信源清单,以及一条“未经交叉证实就不发布”的规则。灾难聊天群里满是言之凿凿的谣言。
- 公开页面保持精简:时间、地点、事实、信源。更正是一等公民。
- 额度和访问权限在原始事件中是真实的约束——在承诺全天候运转之前,先把这条循环的成本算清楚。
为什么它好用
大多数 Grok Bot 文章讲的是个人效率,这个是公民性的:因为两个人在权限和额度上说了一声“可以”,一个实时双语快报在一天之内就立了起来。值得照搬的是那道验证栅栏,而不是英雄事迹。一个会发布未经证实的洪水信息的机器人,比没有机器人更糟。
本案例收集自公开的 Grok Bot 社区,版权归原作者所有。提示词属于参考资料:运行前请先审阅内容, 并且不要让 bot 超出你实际授予的权限行事。