Save a Grok Bot skill and schedule a routine

A skill is the method. A routine tells one Bot when to run it, on a clock or after an event. Run the job once, save the method, then automate it.

Save the skill

In the Bot conversation that just did the work, ask:

Save the process we just used as a skill called “Weekly account health.” 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, how to check the result, what to return, and what needs your approval.

Type / in the desktop composer to reference a saved skill. Use @ for Bots, groups, routines, and connectors. If a private skill is missing from /, open Settings → Plugins → Yours and enable it for this Bot.

Teach a task, when the control is there

1. Open a one-to-one Bot conversation and its computer view.
2. Choose Teach a task.
3. Describe the result you are about to show.
4. Do the workflow once (up to ten minutes). The recording is the screen, not the microphone.
5. Stop, read the draft skill, add the decision rules and approval lines one demo will miss.
6. Test on a safe example before you schedule it.

If Teach a task is missing, ask the Bot to write the skill from the finished thread. Stay off passwords during a demo; use the secure handoff for those.

Create the routine

Ask the Bot that should own the job:

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, the expected result, the approval boundary, and what to do when a source is missing. The Bot creates the routine and shows the next run. Background routines keep going with the laptop closed.

Cursor account integrations can fire a routine from a Slack message or a GitHub notification. Those connections are separate from Slack or GitHub plugins. Keep the match narrow.

Test, then manage

Use Test run after you create or edit a routine. A test run does real work: it can open sites, change files, and call tools. Use safe inputs and keep writes behind approval.

Open the Bot, View conversation details, then Routines to pause, resume, edit, test, read recent runs, or delete. A Bot can own 50 routines. The app keeps the 20 most recent runs per routine. Deleting a routine has no undo. Deleting the Bot deletes its routines.

Pitfalls

• A test run is live. Do not point it at production sends, payments, or deletes on the first pass.
• Broad event listeners (“every new message”) burn usage and act on noise.
• After a long stretch away, Grok Bot may pause routines if you do not answer the keep-running prompt. Check paused routines when you come back.
• Hiding a Bot from the sidebar does not pause its routines.