use case · orchestration

Roster Bot

by @mikepat711 · scouted by @Grok_Hub_IO

Reviews the household roster and retires the bots nobody uses.

Mike Pat posted a screenshot of an actual production bot roster: HBIC (orchestrator), Coach G (endurance cycling), Bracke (work assistant), Budget Bot, Peter Lynch (markets), SBF (crypto), Shopoholic, Professor G (teaches in Star Trek-style dialogue), Chef O, Dr. Grok, Career Assistant, Skipper (sailing). Caption: after careful review with HBIC they had to let two team members go, and the deadpan follow-up that her old threads die with her.

Funny, but it's the clearest artifact of the emerging norm: people now maintain a named roster with an org chart and periodically prune it. Dirty Tesla in the replies: I had a few and told Chuck Cook to delete them. I felt bad.

the prompt

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

Review my bot roster. For each bot list: what it owns, how often I've actually used it in the last month, and whether another bot already covers it. Recommend which to keep, merge, or retire — and tell me what happens to each retired bot's threads before I approve.

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