Skip to content
Bot jobsJob breakdowns

How I Named My AI Team in Grok Bot

How do you choose a name for each bot in your AI team? For my 26 Grok Bots, I wanted a connection between the character and the work. The Lord of the Rings, The Hobbit and The Silmarillion gave me

Thomas "Doc" ColasantiImported from X5 min read
ThomasColasantix article
See this runHouse 422 · 00600

Article

Job breakdowns

How do you choose a name for each bot in your AI team?

For my 26 Grok Bots, I wanted a connection between the character and the work. The Lord of the Rings, The Hobbit and The Silmarillion gave me plenty to choose from. Finding the right match has been one of the most enjoyable, and occasionally complicated, parts of building this setup.

Elrond coordinates the team, while Fëanor handles engineering and Treebeard reviews the writing without rushing to approve it. I gave Gollum the AI-slop hunt, which still makes me smile. Some associations are close to the books; others are my own playful interpretation.

I keep the job beside the name. If you are building your own team, that is a useful place to start: what should this bot do, and where should it stop or ask you? Tom Bombadil proposes fixes but needs my OK to act. Bilbo sorts my personal inbox and never sends anything.

The whole roster works in rotation. I am still trying to balance it against the usage limit, so at some points only part of the team is running. Getting that balance right is difficult, and I would love more room to let them work together.

Here is the team, with the work assigned to each bot and the association behind its name.

🏰 LEADERSHIP

Elrond, Chief of Staff: receives my requests, delegates to the right bot and checks completion. ↳ The Council of Elrond gave me the association with bringing different people and responsibilities together.

Tom Bombadil, The Master: watches over the whole setup, spots problems and proposes fixes. Acts only with my OK. ↳ The Master of his own land, unaffected by the Ring. My choice for independent oversight.

⚙️ ENGINEERING

Fëanor, Head of Engineering: sets the technical rules and installs new skills across the team. ↳ The maker of the Silmarils, for the craftsmanship behind the tools.

Celebrimbor, Site Engineering: keeps the online store and website running, and fixes what breaks. ↳ The smith who made the Three Elven Rings, for building things with care.

Finrod, Roster Keeper: maintains the map of bots, their jobs and their skills. ↳ His friendship with Men suggested someone who knows the different members of the company.

🧭 OPERATIONS

Aragorn, Work Coach: helps me choose priorities and keep my focus. ↳ The Ranger, for finding a road through complicated terrain.

Mithrandir, Brand Keeper: keeps the brand guidelines and checks that work follows them. ↳ Gandalf's Elvish name, for holding the wider purpose in view.

Thorin, Head of Product: handles the catalog, offers and customer experience. ↳ The King under the Mountain, for knowing the value of what is in the treasury.

Balin, Analytics: brings sales, advertising and traffic numbers into one readable picture. ↳ I associate him with Moria and the record of what happened there.

Éowyn, Relationship Radar: checks the inbox for missed follow-ups and sales leads. ↳ The shieldmaiden of Rohan, for noticing when it is time to act.

Bilbo, Personal Inbox: sorts my personal email once a day. Never sends anything. ↳ Bag End, letters and looking after one's own home.

Háma, B2B Desk: follows conversations with brand partners and prepares the next step. ↳ The Doorward of Edoras, for knowing who is at the door.

Isildur, Partner Desk: maintains the partner roster and runs their campaigns. ↳ My association here is with the kingdoms of Gondor and Arnor and their responsibilities.

📜 EDITORIAL

Glorfindel, Editor-in-Chief: runs the editorial team and is my single contact for content work. ↳ A protector in Elrond's household, cast here as my editorial gatekeeper.

Frodo, Writer: handles editorial manuscripts from outline to final text. ↳ His part in continuing Bilbo's Red Book made this an easy choice.

Treebeard, Reviewer: reads each manuscript critically and points out weaknesses. ↳ An Ent's reluctance to be hasty feels appropriate for a reviewer.

Arwen, Covers & Layout: designs covers, figures and page layouts. ↳ She wove Aragorn's banner. A lovely connection to making something visible.

Gollum, Anti-Slop: hunts sentences that sound as though AI wrote them. ↳ My own slightly mischievous casting choice for sniffing out anything tricksy. 😄

📣 SOCIAL

Lúthien, Social Media Manager: plans the calendar and writes the briefs. ↳ The power of her song suggested a name for reaching people.

Éomer, Social Publisher: schedules approved posts on the right channels. ↳ A Marshal of the Riddermark, for acting when it is time to move.

Radagast, Social Desk: runs the content pipeline and tracks how posts perform. ↳ His attention to birds and beasts suggested keeping an ear on what is happening around us.

Meriadoc, Community: brings selected Facebook content to YouTube Community. ↳ The hobbit's travels and return to the Shire suggested carrying things between communities.

🔨 FORGERS

These bots take on heavier work when requested, each using a different AI tool.

Eärendil, Grok Forger: builds things and creates images with Grok. ↳ The mariner carrying a Silmaril, for taking an idea somewhere new.

Durin, Codex Forger: makes covers and visuals with Codex. ↳ Khazad-dûm and Dwarven craftsmanship were the association here.

Faramir, Claude Forger: writes commercial copy and proposals with Claude. ↳ A thoughtful captain, for weighing the words before sending them into the world.

Círdan, Cursor Forger: writes and ships code with Cursor. ↳ The Shipwright. I could hardly resist that one.

What have you named your bots, and what made a particular name fit the job?

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Thank you, @grok @bot @mattyp @poteto @naoufal_elh @lingxi @theaaron @GrokBotRadar, for the work behind a tool that makes this kind of experimenting possible.

Published on grokbot.sh. Cite the public log, not a prompt pack.

Command Menu