Repository Public
1<!-- source: https://docs.x.ai/grok-bot/skills-routines-and-automations (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Work with Grok Bot34# Skills and routines56Turn a successful task into a repeatable process. Grok Bot uses two building7blocks:89* A **skill** is a reusable set of instructions for how to do a task.10* A **routine** tells one Bot when to run a workflow—on a schedule or, where11 supported, after an event.1213Start with a one-time task. Make it reliable, save the method as a skill, and14only then automate it.1516## Save a skill1718A skill captures steps, decision rules, expected output, and safety boundaries.19Skills are available across your Bots, although a Bot may need the relevant20connector or login to use one.2122Ask:2324> Save the process we just used as a skill called “Weekly account health.”25> Include the source systems, risk definitions, output format, and the rule that26> customer contact always requires approval.2728A useful skill states:29301. When to use it312. Required inputs and access323. The sequence of work334. How to validate the result345. What to return356. What requires approval3637Use **Marketplace** in the sidebar to discover and install supported connectors38and packaged skills. Type `/` in the desktop composer to reference a saved skill;39use `@` for Bots, groups, routines, and connectors.4041Private skills are one library shared by all your Bots. If a skill does not42appear in the `/` menu, open **Marketplace → Your plugins → Manage plugins and43skills** and check that it is listed under **Private skills**.4445## Teach a workflow by demonstration4647When **Teach a task** is available, you can demonstrate a browser workflow48instead of describing every step.49501. Open a one-to-one Bot conversation and its computer view.512. Choose **Teach a task**.523. Describe the result you are about to demonstrate.534. Perform the workflow once.545. Stop the recording and review the skill the Bot creates.556. Test it on a safe example before scheduling it.5657Teaching records visible computer interaction for up to ten minutes. It does58not record microphone audio. Avoid exposing secrets during the demonstration;59use the secure handoff flow for credentials.6061The learned skill is a draft. Add decision rules, failure handling, and62approval boundaries that may not be obvious from one example.6364Teach-by-demonstration may be enabled gradually. If the control is not visible,65ask the Bot to create a skill from written instructions and the completed task.6667## Create a routine6869Ask the Bot that should own the recurring job:7071> Every weekday at 8:00 AM, run the Daily customer-risk skill against the72> current account list. Post a linked watch list in this conversation. Do not73> contact customers. If the source data is unavailable, report the failure74> instead of using old data.7576Confirm:7778* The owning Bot79* The schedule and time zone80* The input source81* The expected result82* The approval boundary83* What should happen when a source is missing8485The Bot creates the routine and shows its next run. Background routines can run86while your laptop is closed.8788## Trigger work from an event8990Cursor account integrations can start a routine from an event, such as a Slack91message or a GitHub notification. They are separate from Slack or GitHub92plugins and may require their own connection flow.9394Define a narrow matching rule and a clear response:9596> When a message in `#customer-escalations` contains a support ticket link and97> the phrase “needs repro,” open the ticket, reproduce the issue in staging,98> and post a repro pack in this conversation. Never post back to Slack without99> approval.100101Avoid broad listeners such as “every new message.” They create noise, consume102usage, and increase the chance of acting on irrelevant input.103104## Test before enabling105106Use **Test run** after creating or editing a routine.107108> A test run performs real work. It can navigate websites, change files, and109> call connected tools. Use safe inputs and keep write actions behind approval.110111Review:112113* Whether it selected current inputs114* Whether the output meets the required format115* Whether every action has a source or audit trail116* Whether it stopped at the intended approval point117* Whether failure states are explicit118119## Manage routines120121Open the Bot, choose **View conversation details**, then open **Routines** to122view its routines and recent runs. You can:123124* Enable or pause a routine125* Run a test126* Edit its schedule or instructions127* Inspect recent success and failure history128* Delete it129130A Bot can own up to 50 routines, and the app keeps the 20 most recent run131records for each routine. Deleting a routine is immediate and has no undo.132Deleting a Bot also removes routines owned by that Bot.133134To control unattended usage, Grok Bot may ask whether to keep routines running135after a long period away and pause them if there is no response. Review paused136routines when you return.137138## Design routines for trust139140* Automate preparation before execution.141* Have the Bot draft, reconcile, or recommend first.142* Require approval for sending, purchasing, deleting, publishing, or changing143 production systems.144* Include a no-data and stale-data policy.145* Make retries idempotent where possible.146* Tell the Bot where to report partial completion.147* Re-test after a website, connector, or source format changes.148149See [Settings and notifications](/grok-bot/settings-and-notifications) for time zone150and usage controls, and [Approvals, security, and151privacy](/grok-bot/approvals-security-and-privacy) for automation boundaries.152