Skills and routines

Run it once. Save it as a skill. Then let it run on a schedule. Do not schedule first.

xAI Docs Source xAI Docs ↗

For

You have a weekly job. You want to teach it first, then let it run on its own.

When you're done

A skill you will sign off on. A routine that knows what to do when it fails.

How

01
Do the real job once.
Narrow the scope. Steps, pass/fail, what it delivers, what needs your yes. Edit until you will sign it.
02
Have it save the process you just used as a skill.
Write when to use it, inputs, order, how to check, what it returns. If it needs a walk-through, use Teach a task once, then review the draft it writes.
03
Try it on a second input.
The trial run is real work. Writes still stay parked.
04
Then create the routine.
Write who owns it, which timezone, what to do when data is missing. A background routine still runs when the laptop is closed.
05
Keep event triggers narrow.
Example: a ticket link and needs repro land in the same channel. Do not listen to every new message.

Notes

What's good: you sign the method first. Then it runs overnight. The catch: schedule first, change the rules later, and failures happen while you are gone.

Prompt

存成 skill

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.

https://docs.x.ai/grok-bot/skills-routines-and-automations 原文

排一条工作日 routine

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.

https://docs.x.ai/grok-bot/skills-routines-and-automations 原文

Related plays

Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About