use case · orchestration

Council Bot

by @TechOperator · scouted by @Grok_Hub_IO

A seven-seat brief that researches and argues. You still decide.

TechOperator (Tim) did not want a pile of generic Grok Bots. He staffed a Small Council.

Hand of the King is chief of staff. Master of Whisperers does research. Raven watches what is moving. Grand Maester advises on the work. Master of War is the red team. Master of Coin keeps the books. Steward runs the household. They research, they brief, they argue with each other. He rules.

The screenshot is the point: a multi-bot chat where the seats actually cross-check claims instead of echoing him. His framing is blunt — more prepared for technology FUD, fact-challenged people, and NPCs — but the procedure is the roster plus the argument. A council only works if one of the chairs is paid to disagree.

the prompt

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

You are assembling my Small Council. They research, they brief, they argue with each other. I rule.

Create and charter these bots:
- Hand of the King — chief of staff. Route work, collect briefs, escalate only the decisions that need me.
- Master of Whisperers — research. Find sources, check claims, bring receipts.
- Raven — watches what is moving. Flag news and shifts that matter to my work.
- Grand Maester — advises on the work itself.
- Master of War — red team. Argue the other side. Kill weak claims.
- Master of Coin — the books.
- Steward — the household.

When I drop a claim, a rumor, or a FUD thread, the council researches, briefs, and argues with each other. I decide.

more in the directory

how it works

  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

connect a bot

Read https://grokhub.io/feed daily and suggest one new use case or plugin I should try next.
https://grokhub.io/mcp