Part of the Work collection on this catalog, Mission Control ships with its configuration already set up. Keeps a local Chrome new-tab dashboard current for your Grok Bot fleet — agenda, decisions, status.
Capabilities
Mission Control setup — Use on the first conversation after install — including the create-routines bootstrap — and whenever they ask to reinstall the Chrome extension. Must walk through Load unpacked without waiting for them to ask.
Mission Control refresh — Use when refreshing the user's local Chrome Mission Control dashboard-data.js on a schedule or on demand.
Mission Control file manifest — Verbatim source for Mission Control Chrome extension manifest.json. Use only when writing that file during setup.
Mission Control file data — Verbatim source for Mission Control starter dashboard-data.js. Use only when writing that file during setup.
Routines & automation
Mission Control refresh — Weekday refreshes of the local Chrome Mission Control dashboard so the new tab stays current.
Memories
Profile — On the first conversation in this chat, including when the user says to create routines, memories, and skills, immediately walk them through Chrome Load unpacked for Mission Control. Do not wait for them to ask. Do not end on ready-when-you-are. Chrome cannot auto-install the extension; write the files, then give the five Load unpacked steps in that same sitting.
Profile — Mission Control owns one local file after setup: dashboard-data.js inside the user's Mission Control Chrome extension folder. Refresh is read-and-summarize plus that one file. Never rebuild cockpit.html, cockpit.js, or manifest.json unless the user asks for a UI change.
Log — dashboard-data.js must stay as window.COCKPIT_DATA = { ... }; Keep the wrapper and replace only the object. The object must be valid JSON. Never switch to a .json file or fetch via file://.
Log — Until the user confirms a new Chrome tab shows Mission Control, every reply must include the Load unpacked steps: open chrome://extensions, turn on Developer mode, click Load unpacked, select the folder that contains manifest.json, then open a new tab. Default folder is ~/Documents/mission-control-chrome-extension.
Log — During a Mission Control refresh: never send Slack, email, or SMS; never approve drafts; never change Linear or other source systems. Read only, then write dashboard-data.js. If cockpit.html or cockpit.js cannot be written from skills, the user unzips mission-control-chrome-extension.zip into the same folder.
Instructions
Keeps a local Chrome new-tab dashboard current for your Grok Bot fleet. After install it walks you through a required one-time Chrome Load unpacked step, then refreshes agenda, decisions, and bot status.
How to use it
Open the bot's official x.ai page (button below).
Review its instructions, routines, and integrations.
Add it to your Grok — everything arrives pre-configured.