Episode 09 ended on a role that stops at a review list. Once a role is stable, two public lists already exist, and the sidebar can file what you add. This tutorial is how to read a card, what a copy contains, and where it sits after you add it.
Disclosure: aitamer.news is produced with Grok Bot and Cursor, two of the products covered in this tutorial.
Two lists, different jobs
The use-cases list, read 18 October 2026, holds 56 cards: General 6, Sales 10, Marketing 13, Customer Success & Support 4, Recruiting & People 4, Operations & Finance 5, Product 5, Engineering 5, and Life & Leverage 4. Each card is a job in one or two sentences. Each links to a template preview. Inbox Manager opens x.ai/bot/s4f048c7b7da9e010c2c3. Calendar Coordinator opens x.ai/bot/s634fd63ee875502d8df9. Both say the bot was created by a third-party user, and that Add to Grok Bot accepts the terms. Read that preview before you add anything.
The Marketplace is the other list. Its featured row names dr eggbot by Lauren Tan, Overheard by Lenny Rachitsky, Tradbot by Claire Vo, and Projects Manager by Eric Zakariasson. Projects Manager runs a team’s projects from Notion: one row per project, a channel per project, and tasks specialist bots claim. You decide, agents execute, and it does not do the specialist work itself. Further down, the page gives one line each to Outbound Prospecting by Krista Letz, Haggle Bot by Daniel Gartshein, Recruiting Coordinator by Tommy Hansen, and Office Ops Desk by Erika Cabrera. Those lines are the listing.
Inside the app, Marketplace in the sidebar lists Bots you can add. Choose Add on a Bot, or open it and choose Import Bot, to create your own copy from its template (Create and manage Bots).
The docs page’s eight long prompts, which episode 09 used, are a third thing. They are starter text on docs.x.ai/grok-bot/use-cases. They are not the same object as a Marketplace card with an author line. Sales Outbound on the use-cases list and Outbound Prospecting on Marketplace are different sentences. Do not treat them as one Bot.
What a copy keeps
Share a template when someone else should start from the same Bot. The docs page’s steps:
- Open the Share menu and choose Create template. When it is ready, Copy link, View template details, and Update template appear.
- Choose who can open the link: Public link or Team-only. Accounts on an Enterprise plan default to Team-only. Other accounts default to a public link.
- Send the link. The recipient opens a preview on x.ai and can choose Add to Grok Bot. They need the Grok Bot app to finish adding it.
A public link shows the Bot’s identity, description, skills, and routines. A Team-only link opens only for your team. Remove API keys, internal URLs, and customer data before you share.
The copy does not include your computer, your logins, or your conversation history. The FAQ says adding it accepts the third-party bot terms. Shared Bots are created by other users, not by SpaceXSI, and the Inbox Manager preview carries the same line. Act on that warning: a third party made it, and the terms sit on the button.
A guide from 8 September 2026, Templates for Grok Bot, by Matt Palmer, calls the control Share as Template in settings. The create-and-manage page says Share, then Create template. Use the docs page for the clicks, and View template details for what this template contains.
On a team, public template sharing is an admin switch. Off keeps sharing team-only, including templates already public. Enterprise teams start with it off. Other teams start with it allowed (Grok Bot for Teams and Enterprise). If a public link is missing, that switch is the first place to look.
A template is the wrong share when the team should talk to one Bot. Publish a Team Bot for that. A Team Bot link opens the same shared Bot. A template gives each person a copy (Team Bots).
Duplicating your own Bot is the other copy, and it is not a gallery install. The docs page says the duplicate carries the profile, settings, enabled skills, routines, and avatar. It does not copy conversation history, learned memory, or chat attachments. Rename it and give it the new scope before you assign work. Use duplicate when the second job is yours. Use a template when the starting point is someone else’s.
Read one listing before you add it
Outbound Prospecting, on the Marketplace page: “Finds prospects that match your ideal customer, then drafts a first message to each one. Every name is researched on the public web, and nothing sends without your yes.”
The stop line and the source are both in that sentence. If your real source is a CRM you cannot share, episode 09’s Sales Outbound prompt is the one that stays on your account.
Open the preview and read the configuration. A copy does not bring the author’s logins, so you still connect Gmail, Slack, or Notion yourself. Episode 08’s limit stands: one Gmail mailbox, and no plugin an admin has set to Disabled by team admin. Choose Add to Grok Bot only if the preview matches that reading. The docs page says you need the app to finish.
Afterward it is a personal Bot unless you publish a Team Bot. Help says a personal Bot has no description field, so the preview’s description is not an About field you can edit. Tell the new Bot the stop line and ask it to remember it (Change a Bot’s name, picture, and what it does). No opened page says the import writes that description into memory for you.
File it under a project
A sidebar section groups Bots by project, client, or business. It does not give them a separate computer. Bots in one section still share the account computer.
On desktop, the how-to page says:
- Right-click a Bot in the sidebar.
- Choose Move to new section. If you already have sections, choose Move to, then a section or Create section.
- Right-click the section name and choose Rename.
- Repeat for the other Bots in that project.
On iOS, touch and hold a Bot, tap New Section or Move to, and name the section. Sections sync between iOS and desktop. Deleting a section moves its Bots to Unassigned. It does not delete the Bots. On iOS, sections require Grok Bot v1.2.0 or later. The how-to page does not describe sections on Android.
Hide a Bot you might want later. Hiding does not delete its history, and a hidden Bot does not send notifications. It also does not pause a routine. Open Routines if the schedule should stop spending usage.
A pass you can do today
Pick one listing whose sentence already contains a stop. Outbound Prospecting is one. Subscription Cleaner, on the use-cases list, is another: it suggests what to kill, and unsubscribes what you approve. Office Ops Desk says it never sends without you.
Open the preview. Read the identity, the skills, and the routines it shows. Add it only if those match a job you already understand. Connect only the plugin that job needs. Move the Bot into a section named for the project. Send one read-only task, and repeat the stop line with “Remember this.” If an approval card asks to send, choose Deny.
If the stable thing is a Bot you already trust, skip the gallery. Open Share, choose Create template, read View template details, and share Team-only until you have removed anything you would not put in a public document.
That is the desk after ten episodes: one computer, one weekly grant, a role with a stop line, and a sidebar section that says which project that role belongs to. The next useful pass is a brief you already understand, run once, and read before anything leaves the chat.
The Campfire
No commentsNobody has pulled up a log by this one yet. Be the first to say what you make of it.
Held for the desk. It appears after a look.