HOME / THE HANDBOOK
Grok Bot Skills & Routines Guide
Use a skill for repeatable instructions, a plugin for a tool connection, and a routine for scheduled or supported event-driven work. Start with one successful manual run, then automate the same clearly defined task.
Independent guide based on linked official documentation. Examples below are suggested workflows, not product benchmark results.
Grok Bot skills, routines and plugins: the difference
| Component | Purpose | Example we suggest |
|---|---|---|
| Skill | Reusable task instructions | Turn supplied articles into a sourced research draft |
| Routine | Assign a workflow to a Bot and a trigger | Prepare that draft every Monday morning |
| Plugin | Connect tools and packaged capabilities | Read from your authorized document service |
Skills describe the procedure; routines decide when it runs. Event triggers depend on available integrations. Use / to reference a skill. Installed and private skills appear under Settings → Plugins. Official skills and routines guide ↗
For a connector, add it through Settings → Plugins, complete authentication and attach it with @. Installing it does not necessarily finish sign-in. Connect an app ↗
Build a Grok Bot skill from a working task
We recommend defining the input, steps, output and exceptions in plain language. Here is an original starter specification:
Input: the public URLs I supply. Read each source and note its date. Group confirmed changes by product. Output a draft with a source link for every factual item and a separate list of unavailable pages. Never fill a gap with a guessed fact. Ask before using additional sources.
Try the instructions on two pages before saving them as a skill. A useful acceptance check is whether another person can trace each statement to its source without opening the conversation history.
Where available, Teach a task can turn a recorded browser workflow into a draft skill. Review and test the draft; this feature is rolling out gradually. Teaching a workflow ↗
Create a scheduled Grok Bot routine
On desktop, open the Bot’s conversation details and Routines. Define the workflow and trigger. A routine belongs to one Bot, and a test run performs real work. Routine controls ↗
For our example, choose a weekly research draft with a short source list and a named destination file. State how the Bot should handle a missing page and whether it should overwrite or create a new draft. Leave sending or publishing as a separate reviewed action.
Check the timezone in Settings → General → Agent before saving the schedule. Schedule timezone ↗
Test before leaving a routine running
- Use a sample with a known result, including one unavailable source.
- Check that the output includes the requested links, date and unknowns.
- Inspect the destination: was the right file created, updated or duplicated?
- Review the usage meter after the run before increasing frequency.
- Confirm that no external message or publication occurred without the intended review.
These checks help separate an instruction problem from a connection problem. Keep the first recurring version small enough that you can inspect its entire output.
Why is a Grok Bot routine not working?
If the output is incomplete, first try the same skill manually. Check its inputs and the connected account. A browser login can expire, requiring you to take over and authenticate again. Persistent sessions and sign-in ↗
If the timing is wrong, inspect the trigger and timezone. If you want to stop work, pause the routine itself: hiding a Bot does not pause its routines. Hiding a Bot ↗
Mobile supports pausing and resuming, but routine editing, history and testing currently require desktop. Mobile routine controls ↗ For billing-related interruptions, check the usage and pricing guide.