Skill 和 Routine

Turn a successful task into a repeatable process. Grok Bot uses two building blocks: a skill is a reusable set of instructions for how to do a task; a routine tells one Bot when to run a workflow—on a schedule or, where supported, after an event. Start with a one-time task. Make it reliable, save the method as a skill, and only then automate it.

把一次干成的活，变成可重复的流程。Grok Bot 用两块积木：skill 是一套可复用的「怎么干」；routine 告诉一个 Bot 何时去跑——按日程，或（支持时）按事件。先做一次性任务。干稳了，把方法存成 skill，最后才自动化。

A skill captures steps, decision rules, expected output, and safety boundaries. Skills are available across your Bots, although a Bot may need the relevant connector or login to use one. Ask it to save the process you just used, and include the source systems, risk definitions, output format, and the rule that customer contact always requires approval. A useful skill states when to use it, required inputs and access, the sequence of work, how to validate the result, what to return, and what requires approval. Use Settings → Plugins to discover and install supported connectors and packaged skills. Type / in the desktop composer to reference a saved skill; use @ for Bots, groups, routines, and connectors. Installed private skills can be enabled per Bot. If a skill does not appear in the / menu, open it under Settings → Plugins → Yours and enable it for the current Bot.

skill 记下步骤、判断规则、预期产出、安全边界。skill 对你的 Bot 通用，但某个 Bot 要用，可能还得有对应的连接器或登录。让它把刚才那套存下来，写上源系统、风险定义、输出格式，以及联系客户必须先批。好 skill 要写清：何时用、要哪些输入和权限、干活顺序、怎么验收、交什么、什么必须先批。用 设置 → Plugins 发现并安装支持的连接器和打包 skill。桌面输入框打 / 引用已存 skill；@ 用来点名 Bot、群、routine、连接器。装上的私有 skill 可以按 Bot 启用。/ 菜单里没有，就打开 设置 → Plugins → Yours，给当前这个 Bot 打开。

When Teach a task is available, you can demonstrate a browser workflow instead of describing every step. Open a one-to-one Bot conversation and its computer view, choose Teach a task, describe the result you are about to demonstrate, perform the workflow once, stop the recording, and review the skill the Bot creates. Test it on a safe example before scheduling it. Teaching records visible computer interaction for up to ten minutes. It does not record microphone audio. Avoid exposing secrets during the demonstration; use the secure handoff flow for credentials. The learned skill is a draft. Add decision rules, failure handling, and approval boundaries that may not be obvious from one example. Teach-by-demonstration may be enabled gradually. If the control is not visible, ask the Bot to create a skill from written instructions and the completed task.

有 Teach a task 时，你可以演示一遍浏览器流程，不必逐步口述。打开一对一 Bot 对话和电脑画面，选 Teach a task，先说你马上要演示的结果，做一遍，停录，再审它起草的 skill。挂日程之前，先用安全例子测。教学最多录十分钟看得见的电脑操作，不录麦克风。演示时别暴露秘密；凭证走安全交接。学来的 skill 是草稿。一次例子看不出的判断规则、失败处理和审批边界，你要补上。这个功能可能分批开放。控件看不见，就让 Bot 根据书面说明和刚干完的活来建 skill。

Ask the Bot that should own the recurring job, for example: every weekday at 8:00 AM, run the Daily customer-risk skill against the current account list; post a linked watch list in this conversation; do not contact customers; if the source data is unavailable, report the failure instead of using old data. Confirm the owning Bot, the schedule and time zone, the input source, the expected result, the approval boundary, and what should happen when a source is missing. The Bot creates the routine and shows its next run. Background routines can run while your laptop is closed.

问那个该负责循环工作的 Bot。比如：每个工作日早上 8 点，用「每日客户风险」skill 跑当前客户名单；在这个对话里贴一份带链接的观察名单；不要联系客户；源数据没有，就报失败，别用旧数据。确认：哪个 Bot 负责、日程和时区、输入从哪来、预期结果、审批边界、源缺失时怎么办。Bot 建好 routine 并显示下次运行。笔记本合上，后台 routine 也能跑。

Cursor account integrations can start a routine from an event, such as a Slack message or a GitHub notification. They are separate from Slack or GitHub plugins and may require their own connection flow. Define a narrow matching rule and a clear response, and never post back to Slack without approval if that is your boundary. Avoid broad listeners such as “every new message.” They create noise, consume usage, and increase the chance of acting on irrelevant input.

Cursor 账号集成可以从事件启动 routine，比如一条 Slack 消息或一次 GitHub 通知。这和 Slack / GitHub 插件不是同一套，可能要另走连接流程。匹配规则要窄，回应要清楚；你的边界若是没批准绝不回帖到 Slack，就写死。别做「每条新消息都听」这种宽监听。又吵、又耗用量，还更容易对不相干的输入动手。

Use Test run after creating or editing a routine. A test run performs real work. It can navigate websites, change files, and call connected tools. Use safe inputs and keep write actions behind approval. Review whether it selected current inputs, whether the output meets the required format, whether every action has a source or audit trail, whether it stopped at the intended approval point, and whether failure states are explicit.

建完或改完 routine，用 Test run。试跑是真干活：会打开网站、改文件、调用已连工具。用安全输入，写入动作放审批后面。检查：它是不是选了当前输入、输出格式对不对、每个动作有没有来源或审计痕迹、有没有在你设定的审批点停住、失败状态说没说清楚。

Open the Bot, choose View conversation details, then open Routines to view its routines and recent runs. You can enable or pause a routine, run a test, edit its schedule or instructions, inspect recent success and failure history, and delete it. A Bot can own up to 50 routines, and the app keeps the 20 most recent run records for each routine. Deleting a routine is immediate and has no undo. Deleting a Bot also removes routines owned by that Bot. To control unattended usage, Grok Bot may ask whether to keep routines running after a long period away and pause them if there is no response. Review paused routines when you return.

打开那个 Bot，选 View conversation details，再打开 Routines，看它的 routine 和最近运行。你可以启用或暂停、试跑、改日程或说明、看最近成败、删除。一个 Bot 最多 50 个 routine，每个 routine 留最近 20 条运行记录。删除立即生效，不能撤销。删 Bot 也会带走它名下的 routine。为了控制没人看着的用量，离开太久时 Grok Bot 可能问你还要不要跑；没回应就暂停。回来后把暂停的 routine 看一遍。

Automate preparation before execution. Have the Bot draft, reconcile, or recommend first. Require approval for sending, purchasing, deleting, publishing, or changing production systems. Include a no-data and stale-data policy. Make retries idempotent where possible. Tell the Bot where to report partial completion. Re-test after a website, connector, or source format changes.

先自动做准备，再执行。让 Bot 先起草、对账、或给建议。发送、采购、删除、发布、改生产系统，必须先批。写清没数据和数据过期怎么办。能做到的话，重试要可重复执行。部分完成报到哪里，也要告诉它。网站、连接器、源格式一变，就重新测。