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 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.

App access: each person's own account vs. one shared key — On a Shared Bot (Shared Bots were formerly called Team Bots), the apps and secrets the owner adds work the same for everyone, while a connected account always acts as the person the Bot is answering and is never used for someone else. Choose per tool: each person's own account for anything that creates records (Linear, Jira), a scoped read-only key added as a secret for shared lookups (monitoring).
Custom MCP servers: adding one by URL or by command, and where credentials belong — A Bot can add an MCP server that isn't in the catalog by URL, or by a command that runs on its computer (a command-started server is then available to your other Bots too); adding one on a private network or with a private certificate authority asks for your approval first. Keep tokens out of the command, its args and chat: hand them over as secrets, and expect an Enterprise MCP allowlist to block unapproved servers.
Bot secrets: secure handoff, who can use them, and keeping keys narrow — For your own Bots, enter an API key in the secure secret card when the Bot asks: the field is masked and the value isn't written into chat or shown to the Bot. On a Shared Bot, Secrets in Bot settings work the same for everyone who chats with it, so add only clearly named, scoped, read-only service-account keys everyone you share with may use.
Event routines from GitHub and Slack, and webhooks — A routine tells one Bot when to run: on a schedule or after a Slack message, a GitHub, Linear, Sentry or PagerDuty event, an email to the Bot's own address or a webhook POST. Ask for it in chat, confirm owner, time zone, input, result and approval boundary, test it, then manage it from the Bot's Details tab.
Narrow matching rules and safe retries that don't act twice — Match on specific signals (a channel plus a ticket link plus "needs repro") instead of any message. Make retries idempotent (check for existing work first), report partial completion, and remember approvals raised by unattended work expire after 30 minutes.
Skills with validation steps and failure handling — Write skills that state when to use them, inputs and access, steps, how to validate the result, what to return and what needs approval; add a failure path for missing or stale data. Use Teach a task (when available, desktop) for browser workflows, then fix the draft.
Delegate coding to Cloud Agents and receive their files — Ask the Bot to hand a scoped coding task to a Cursor Cloud Agent and attach the returned files; review them like any pull request. Admins can turn delegation off.
Shared Bots: build a simple engineering Shared Bot with a read-only key and share it — Use + → Create a Bot, tell it in a sentence what it helps the team with, then fill Bot settings (wrench icon: Plugins, Secrets, Skills, Files) with skills that already work and a read-only key, and write a one-sentence description under About. Share it from the Bot's name → Share → Who has access → your team; teammates add it from Browse shared Bots.
Engineering Pages: build health and incident trackers — Have a Bot build a Page (charts, heat maps, tables) for service health or open incidents and keep it current with a routine. Pages start private and can be shared with people you invite, your team or anyone with the link; Pages may not be available yet on Enterprise teams, so check your screen and keep internal data off link-shared Pages.
Capstone: an event-triggered reproduction routine with an approval stop — Combine a validated repro skill, a narrowly matched Slack or GitHub trigger, idempotent retries and an approval stop before anything is posted, then test it before enabling and add the skill to a small engineering Shared Bot.

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

Software engineers, SREs, QA engineers and technical operators. The material is pitched at intermediate level, and takes roughly 180 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 branching scenario, code lab, guided lab exercises. There is no video to sit through and no slide deck to click past.

Understanding is checked with a tool 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: 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'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.
Cursor & Grok Bot for Developers Pathway — One path for engineering teams that use Cursor with Grok Bot included. A placement check for each tool sends you to the right Cursor course and the right Grok Bot course. Also includes 8 optional playbooks (Testing, Code Review, Refactoring & Migration and Docs & Onboarding for Cursor; Testing, Code Review, Incidents & Performance and Docs & Onboarding for Grok Bot) to take any time after Essentials; they don't count toward the certificate.
Grok Bot for Developers Pathway — Grok Bot for engineers and technical operators: Bots for engineering work, custom connections and secrets, event-triggered routines, engineering Shared Bots (formerly called Team Bots), and administering and securing Grok Bot across a company. Also includes 4 optional playbooks (Testing, Code Review, Incidents & Performance, Docs & Onboarding) 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 180 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-DEV-201.