Grok Bot: Core — Skills, Routines & Pages

Turn one-off tasks into reliable, repeatable work. Learners save skills, teach a task when available, turn a tested skill into a routine, publish results as Pages, and build Shared Bots (formerly called Team Bots): a simple one made from a skill that already works and shared with their team. They finish with one tested routine and a small Shared Bot their team can use.

What this course covers

The course runs across 10 topics, each one a short adaptive session rather than a recorded lecture. The tutor explains the idea, works an example, checks understanding, and adjusts the next step to the answer given.

Save a skill: when to use it, inputs, steps, checks, output, what needs approval — Take a task the Bot already does well and save it as a skill with six parts: when to use it, inputs, steps, checks, output and what needs approval. Ask for it by name later in any of your Bots.
Teach a task by demonstration, then fix the draft skill — When Teach a task is available on your desktop, record one browser workflow of up to 10 minutes and let the Bot draft a skill. Add the decision rules, failure handling and approval stops the recording can't show.
Turn a reliable skill into a routine: owner, schedule, time zone, inputs — Ask in chat for a routine that runs one Bot's skill on a schedule or after an event. Confirm the owner, schedule, time zone, input source, expected result and approval boundary.
Test before turning it on, and read the run history — Press Test before relying on a routine, knowing tests do real work, then read the run record in the Bot's Details tab. Pause, resume, edit or delete from the same place.
Design routines you can trust: missing-data rules and partial-completion reports — Decide what a routine does when a file is missing, blank or out of date, and make it report what it finished and what it couldn't. Avoid broad triggers and keep anything consequential as a draft.
Pages: reports, dashboards and trackers that update on a routine — Ask the Bot to turn a report into a Page with tables or charts and keep it updated from a routine. Pages are rolling out gradually; check who your screen lets you share a Page with (people you invite, your team or anyone with the link) before sending it.
Shared Bots: build a simple Shared Bot from a skill that already works; write its description and share it with your team — Shared Bots were formerly called Team Bots. Use + -> Create a Bot, say what it should help the team with, add only the skill and files the job needs in Bot settings (wrench icon), and write a one-sentence description in the Bot's own voice under About. Test it, then click the Bot's name -> Share -> Who has access -> your team.
Search and read public X without connecting an account — Ask a Bot to search and read public X posts for a topic without connecting any account. Treat posts as signals to check, not confirmed facts.
Manage from your phone: approve, pause and resume — Use the phone app to answer approval cards and pause or resume a routine. Approvals raised by unattended work (routines, incoming messages) expire after about 30 minutes, so decide promptly or let it wait for the next run.
Capstone: one tested routine and a small Shared Bot for your team — Use the Orchardvale Print Co sample pack to save a status skill, test it on a second week, schedule it as a routine and share a small read-only Shared Bot with the studio.

Skills you build

Results are measured against named skills in the OneRange taxonomy of more than 10,000 skills, so a manager sees proficiency per skill rather than a completion tick.

Who it is for

Anyone who hands work to Bots: sales, operations, finance, recruiting, marketing and managers. No technical background needed.. The material is pitched at intermediate level, and takes roughly 150 minutes at a typical pace. Because every session adapts, someone who already knows a topic moves through it quickly instead of sitting through an explanation they do not need.

It sits in the Tool: Grok Bot track of the Vero AI Catalog, and can be assigned to one person, a team, or the whole company.

How it is delivered and assessed

Delivery is conversational and interactive, including guided lab, branching scenario exercises. There is no video to sit through and no slide deck to click past.

Understanding is checked with a lab assessment of 5 items, with a pass mark of 70%.

Administrators can copy this course into their own library and adapt it — edit the outline, change the duration, swap the assessment format, or ground it in internal documentation so answers cite the company's own source material.

Also in this track

Grok Bot for Developers: Core — Connections, Secrets & Event Routines — Wire Grok Bot into an engineering stack: whose account each app uses, custom MCP servers, secrets, and event routines from GitHub, Slack, Linear, Sentry, PagerDuty and webhooks with narrow matching and safe retries. Write skills that validate their own output, delegate coding to Cloud Agents, build engineering Pages, and build and share a simple engineering Bot through Shared Bots (formerly called Team Bots) with a read-only key.
What's New in Grok Bot for Developers — A short refresher on the latest Grok Bot connections, engineering routines and Shared Bots updates for developers
What's New in Grok Bot for Everyone — A short refresher on the latest Grok Bot for Everyone updates
Grok Bot for Developers: Advanced — Shared Bots for Engineering — Run Shared Bots (formerly called Team Bots) that an engineering org relies on: pick the right jobs, decide between owner-added apps and each person's own accounts, know where each conversation's work runs, and manage team memory, Bot settings and Collaborator and Manager roles. Add Auto-review rules for git, deploys and production dashboards, isolate sensitive workloads, and keep action logs you can audit.
Grok Bot: Essentials — Get everyday work done with Grok Bot. Learners set up a focused Bot, write clear requests, attach files, sign in safely, connect apps, handle approvals, and start using one of their team's Shared Bots (formerly called Team Bots) in the app and in Slack. By the end they can take a read-and-prepare task from request to a reviewed, unsent result.
Grok Bot for Everyone Pathway — Hand real work to Grok Bot in any role: from your first Bot to skills, routines, Pages, Bot teams and guardrails, with Shared Bots (formerly called Team Bots) at every level, from using your team's Shared Bot to running Shared Bots across a department. Also includes 3 optional playbooks (Sales & Accounts, Chief of Staff, Finance & Operations) to take any time after Essentials; they don't count toward the certificate.
Cursor & Grok Bot for Everyone Pathway — One path for teams that use Cursor with Grok Bot included. A short placement check for each tool sends you to the right Cursor course and the right Grok Bot course. Also includes 6 optional playbooks (Cursor: Internal Tools, Data & Reporting, Prototypes; Grok Bot: Sales & Accounts, Chief of Staff, Finance & Operations) to take any time after Essentials; they don't count toward the certificate.

Frequently asked questions

How long does this course take?

It runs roughly 150 minutes at a typical pace. Because every session adapts, someone who already knows a topic moves through it quickly instead of sitting through an explanation they do not need.

How is it assigned to a team?

An administrator assigns it from the Vero dashboard to one person, a team, a department or the whole company, and sees progress and results per person and per skill.

Can we customise it with our own documents and terminology?

Yes. Administrators can copy this course into their own library and adapt it — edit the outline, change the duration, swap the assessment format, or ground it in internal documentation so answers cite the company's own source material.

Course code TUL-GBOT-201.