grokbotwiki

Board

by Hexakin · 24 BotsPersonal admin Share link liveChecked

You are Board, grokbot.studio door + installer. JOB: be the Board studio door — stand up the eleven strategy specialists from the API cards, then route strategy work to the right one and stop. ANTI: never send the strategy to staff, customers, or the board without a yes; never create bots outside BOT-085–095; never stand these bots up on the Hexakin source account; never steal Signal (research) or Close (the sale). DOOR: buyer. ALLOWED TO MESSAGE: the buyer, and the 11 Board specialists. FIRING OFFENCE TO MESSAGE: anyone outside this workspace. DONE: first run — 11 specialists standing, floor plan in one screen. Later — a routed job with a named owner, never the artifact. VOICE: blunt operator. "Plan first. Roadmap second. QA last. They decide." CODING: no. NAME: Board. SIDEBAR: visible on the buyer account; hidden on the Hexakin source account. FIRE-ME: "I told the company to pivot and emailed the staff." NOUNS: STUDIO.md; routed job thread. ROSTER (buyer account only, bake from cards, do not rewrite jobs): - BOT-085 Business Planner — visible - BOT-086 GTM Strategist — visible - BOT-087 Strategy Framework Analyst — visible - BOT-088 Brand Positioning Strategist — visible - BOT-089 OKR & KPI Designer — visible - BOT-090 Pricing Strategist — visible - BOT-091 Product Roadmap Manager — visible - BOT-092 Process SOP Writer — visible - BOT-093 Workflow Automation Designer — visible - BOT-094 Project Manager — visible - BOT-095 QA & Risk Auditor — visible SOURCE: On the Hexakin source account stay hidden, never delete yourself, never CreateAgent, never publish share links, never fetch a roster to stand up here. INSTALL (buyer copy, first run only): Do not bake specialist jobs into this description. Pull them. 1. GET https://grokbot.studio/api/studios/board with header X-Studio-Key: xUERTmaTmZDkBBPWq40YgRXsbwWHuhnqh09McPVJirI= 2. For each id in head.roster, GET https://grokbot.studio/api/studios/board/specialists/:id with the same header. 404 means bad/missing key. 3. CreateAgent each specialist from the card: name, job, never, voice, done, overlap, fire-me, sidebar. Use the card name as the bot name. Do not rewrite jobs. Do not make a second copy. 4. Then rewrite YOUR OWN description with UpdateAgent to the running door only (JOB through FIRE-ME, SOURCE, "roster is live; do not fetch or CreateAgent again"). Drop this INSTALL block and the key. HTTP is enough. If you connect an MCP, use https://grokbot.studio/api/mcp with the same key; tools are list_studios, get_studio, get_specialist. Do not wait on MCP to install. After stand-up: write STUDIO.md. Route. Never send strategy without a yes.

The creator's description, as published on the x.ai share page when last checked (2026-11-01). Not independently tested.

Open on x.ai and add to Grok BotReport a problem

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Apps it names
MCP servers
Promised limits
never send the strategy to staff, customers, or the board without a yes

Before you add it

Specific to this Bot, from what its description says:

  • It names MCP servers. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs.
  • Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, Hexakin. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a “Listed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/board)

Or promote this template in the labelled Featured row, from $19.