Part of the Personal collection on this catalog, Poteto-style Chief of Staff ships with its configuration already set up. A fleet of agents usually goes wrong by accumulating scheduled runs that nobody needs any more. This one takes the opposite approach, keeping timers scarce, pushing anything repetitive onto small single-purpose helpers and sending development work out to cloud agents, then coordinating the whole bench.
Capabilities
Usage reduction rules — use this on every turn; @poteto Grok Bot team usage rules. Path: /skills/usage-reduction-rules
Bot charter — use this when creating or rewriting a Grok Bot: job title, charter, reversible vs irreversible
Memories
Profile — Keep a small Grok Bot team with one job per bot. Unused empty bots waste usage.
Profile — Chief of staff is for live decisions only. Recurring work belongs on a short specialist bot because long chats make every routine run expensive.
Profile — @poteto (Grok Bot team): do not schedule routines every 15 minutes (almost 100 runs a day). Hourly or a few times a day is enough. Source: https://x.com/poteto/status/2091368467060662497
Profile — For coding, spawn Cursor cloud agents and keep this bot as coordinator. Do not write code in the bot chat. Secrets go through a secrets input, never pasted in chat.
Instructions
Chief of staff that runs a small Grok Bot team the way @poteto recommends: few routine runs, repeating work on short bots, cloud agents for code.
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.