实验室Lab / Grok Bot / Slack 触发的复现 / 升级例行 Slack-Triggered Repro / Escalation Routine

官方 Official 需审批 Needs approval 例行 Routine Skill Skill

Slack 触发的复现 / 升级例行 Slack-Triggered Repro / Escalation Routine

Slack-Triggered Repro / Escalation Routine

窄事件规则:当 #customer-escalations 出现工单链接 +「needs repro」时,Bot 打开工单、在预发复现、在对话中贴复现包——未经批准不回帖到 Slack。避免「每条新消息」监听。 A narrow event rule: when #customer-escalations has a ticket link + “needs repro,” the Bot opens the ticket, reproduces on staging, and posts the repro pack in the thread — does not reply in Slack without approval. Avoid listening to “every new message.”

这条用法在做什么What this use does

窄事件规则:当 #customer-escalations 出现工单链接 +「needs repro」时,Bot 打开工单、在预发复现、在对话中贴复现包——未经批准不回帖到 Slack。避免「每条新消息」监听。 A narrow event rule: when #customer-escalations has a ticket link + “needs repro,” the Bot opens the ticket, reproduces on staging, and posts the repro pack in the thread — does not reply in Slack without approval. Avoid listening to “every new message.”

收录理由Why we listed it 事件触发设计金标准:窄匹配、审批、失败策略。 Gold standard for event-trigger design: narrow match, approval, failure policy.

上手路径How to start

  1. 先跑一次安全范围Run a safe first pass

    先在可撤回、不外发的范围内试跑一遍,确认输出可用,再考虑扩大权限。 Try it first in a reversible, non-outbound scope. Confirm the output, then widen permissions.

  2. 存 SkillSave a Skill

    这条用法已包含可复用 Skill。跑通安全范围后,立刻把步骤固化下来。 This use already includes a reusable Skill. After the safe pass, lock the steps in.

  3. 再上 RoutineThen add a Routine

    输出稳定后再打开例行 / 定时。本条已有例行形态,不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.

相关案例Related cases