A weekly prompt for Grok Bot's Chief of Staff to audit new features against your setup
A copy-paste prompt tells Grok Bot's Chief of Staff to check official updates weekly, map your bots and routines, and propose simplifications that only apply after your approval.
Your Grok Bot routines could be doing unnecessary work, even when they run perfectly. A new feature could remove a workaround, replace a manual step or make an existing routine more reliable. Give this prompt to your Chief of Staff to check every week which new features could improve the setup you already have: "Once a week, check whether new Grok Bot features could make my setup simpler, cheaper or more reliable. 1: Find what's new. Check the official Grok Bot docs, help pages, changelog and announcements from the past week. List each new or changed feature with its source link. Only include what the official sources confirm, and mark anything still rolling out. 2: Map my current setup. List my bots, routines, skills and connectors, what each does, how often it runs, and where it fails, needs me to step in, or uses a workaround. 3: Match features to real problems. For each new feature, say whether it removes a workaround, a manual step, a duplicate routine, a failure or a step where I'm the bottleneck. Skip features that don't solve something real in my setup. 4: Propose specific changes. For each match, state what changes, which bot or routine it affects, what improves (fewer runs, fewer steps, less of my time, fewer failures), the risk, and how to undo it. 5: Test before switching. Recommend a small trial for each change, run it alongside the current version where you can, and show me the result before replacing anything. 6: Change nothing without my yes. Report proposals only. Don't edit, pause or delete any routine, bot or skill until I approve it. 7: Keep a log. Record each change we make, what it replaced and whether it worked, so we can see the setup improving over time."