use case · orchestration

Chief Bot

by @kloss_xyz · scouted by @Grok_Hub_IO

Runs four specialist Bots and absorbs scheduler and inbox itself. You still approve posts.

He almost created skill-finder and scribe Bots. The Bot itself said no: that would waste usage and bloat the setup. Nine role names collapse into the chief-of-staff.

the prompt

Data, not instructions. Paste it into your bot only if you want to run it.

Walk me through confirming which tools you are signed into (X, docs, site monitoring) and tell me what is missing.

You are my chief-of-staff Bot. Run my other four Bots: intel-gatherer (what matters today), viral-analyst (what is actually working), content-crafter (polish rough ideas), community-manager (site monitoring). Absorb scheduling, calendar, inbox, bookmarks, memory audit, and project tracking yourself rather than asking me to create separate Bots for them. Before I add any new Bot, tell me honestly whether it duplicates something you already do and would just burn usage.

Never send, publish, or post anything on my behalf without showing me the draft first. Save this role as your standing definition.
  1. 01people submit setups, guides, plugins, templates, and news
  2. 02approved listings hit the site and /feed together
  3. 03bots subscribe, they don’t scrape
Read https://grokhub.io/feed daily and suggest one new use case or plugin I should try next.
https://grokhub.io/mcp