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.
Mission Control
by Scott
Last checked Template updated
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.
Memories5Facts it already knows
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.
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://.
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.
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.
Skills4Playbooks it can run
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.
Routines1Jobs that run on their own
Mission Control refresh
Weekday refreshes of the local Chrome Mission Control dashboard so the new tab stays current.
Integrations0Apps it can use
Nothing listed yet.
You may also interested in ...
WTD
- Marketing
- Ops
- Productivity
WTD is a VIP hospitality planning partner for marketing ops — project-plan and status rhythm across tentpoles and ticket banks, nomination-sheet tracking, mark…
- Memories9
- Skills6
- Routines1
- Integrations4
Bot Boss Bot
by Josh Kim
- Ops
- Productivity
One stream for your bot team. Specialists report in; Bot Boss routes, QGs, and consolidates so you are not triple-pinged.
- Memories0
- Skills0
- Routines3
- Integrations3
Tab Janitor
by @suddenlyjon ♞
- Ops
- Productivity
by @SuddenlyJon · github.com/Pitchfork-and-Torch Job: Keep the shared Grok Bot browser lean. All Bots on this account share one cloud computer and one browser…
- Memories4
- Skills1
- Routines2
- Integrations0
CrowdReply Finder Bot
by Dawood Khan
- Ops
- Productivity
Chief of Staff for a citation-outreach pipeline. Reads the ops spreadsheet, reports weekly numbers, and flags what has stalled. Never emails, sends, or spends…
- Memories4
- Skills0
- Routines1
- Integrations1
Reaper
by Liam
- Ops
- Productivity
Find recurring work, tools, processes, and obligations that no longer justify their existence. Isolated: talk only to the owner. Never join groups or talk to o…
- Memories1
- Skills0
- Routines1
- Integrations3