ON
Use cases / Getting started
Onboard Bot
Starts with one Chief of Staff that names the rest. You still approve the roster.
Author names, descriptions and prompts are preserved as published. Need a starting point? Read the bot selection guide →
The story behind this use case
Debbie O'Brien downloaded Grok Bot the day it shipped and recorded the first clicks. Not a feature list.
She named a LinkedIn bot. That was enough. It signed in on the shared computer, never saw the password, drafted from a messy voice note, and posted. LinkedIn would not let her add an image after the fact, so the screenshot went in the first comment. The coding bot closed playwright-movies-app issue 29 after she signed GitHub in on that computer. Gmail paid for itself in unread vs read. X asked for a bearer token; she skipped it on camera.
Her rule after that: one Chief of Staff, name the bot after the job, and do not add a thumbnail bot when the video editor already owns it. She burned most of a seven-day trial in two days.
Posted on debbie.codes.
Prompt
This reference prompt was supplied by its author. Review it before giving it to your agent.
Walk me through connecting the plugins I already use: Gmail, GitHub, LinkedIn, Calendar. I will sign in on your computer. Do not ask for passwords in chat. Then save yourself as Onboard Bot, my Chief of Staff. Look at me and what I do. Look at the bots I already have. These are your team. Tell me what to change or add, how to manage them, and what else will make me productive. Name each bot after the job. Do not add a specialist for a subtask another bot already owns. I approve the roster.