Save a skill in Grok Bot

A skill is a reusable set of instructions for how to do a task: the steps, decision rules, expected output, and safety boundaries. After a one-time run works the way you want, ask the Bot to save that method so any of your Bots can call it later. Official guide: Work with Grok Bot → Save a skill.

Skills sit between a finished one-off task and a scheduled routine. Teach the method once (by message or by demonstration), save it as a named skill, then put a routine on top only when the timing should repeat. For demonstration recording see Teach a task in Grok Bot. For schedules and event listeners see Save a Grok Bot skill and schedule a routine.

Ask the Bot to save the process

In the conversation that just finished the work, ask directly:

Save the process we used for this task as a skill called "Weekly account health". Include the source systems, risk definitions, output format, and the rule that customer contact always requires approval.

Name the skill for the job you will search later. Point at the sources, the risk or acceptance rules, the output shape, and every action that must stop for your approval. The Bot writes those into the skill so future runs do not rely on chat memory alone.

What a useful skill states

Include all of the following when you ask the Bot to save:

1. When to use it — the trigger or job the skill is for.
2. Inputs and access — files, lists, plugins, or logins the run needs.
3. Sequence of work — the ordered steps that produced the good result.
4. How to validate — checks that prove the output is ready.
5. What to return — the artifact shape (spreadsheet columns, linked watch list, draft location).
6. Approval boundaries — sends, purchases, deletes, publishes, and customer contact that must wait for you.

Skills are available across your Bots. A Bot may still need the relevant plugin or login before a skill that depends on that access can run. Install and authenticate connectors under Plugins when the skill calls them.

Reference the skill with /

Type / in the composer to reference a saved skill while you message the Bot. If a private skill does not appear in the / menu for the current Bot, open Settings → Plugins → Yours and enable that skill for this Bot. Marketplace skills and packaged skills show under Plugins as well; private skills you saved stay under Yours until you enable them per Bot.

Before you schedule

Run the skill once on a safe input after you save it. Confirm it still selects current sources, stops at the approval points you named, and returns the format you asked for. Only then ask the owning Bot to create a routine that calls the skill on a schedule or after a narrow event. A draft or untested skill is not ready to automate.

Pitfalls

• Saving before the one-off method is reliable — fix the process in chat first, then capture it.
• Leaving approval boundaries out of the skill text — routines that call a loose skill can send or change production systems without stopping.
• Expecting every Bot to see a private skill in / immediately — enable it under Settings → Plugins → Yours for that Bot when it is missing.
• Skipping the safe retest after you edit steps, sources, or plugins the skill depends on.