All use cases

Engineering

One job per bot, a never-do list, and a weekly skill staleness checker

Bot fleets get messy when how-tos rot inside private chats instead of shared skills.

Share

What hurt

grovr (@grovr_au) keeps setup clean: each bot gets one job plus a short never-do list naming which bot handles those instead; how-tos live in shared skills; one bot's whole job is checking those skills every week for anything stale — and it verifies outputs landed where expected (chat, Slack, …). Not affiliated with xAI.

What to install or create

One job + never-do → shared skills → weekly staleness + output check.

Bots

  • Role bots

    Each owns one job and a never-do list.

  • Skill auditor

    Weekly: find stale skills and verify outputs landed.

Plugins

  • None on day one. Follow the first-run steps.

Routines

  • Weekly skill audit. Weekly. Scan shared skills for stale steps; check outputs landed.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read https://x.com/grovr_au/status/2111594375260111249 (credit @grovr_au).
  2. 2Give each bot one job and a never-do list pointing to the right bot.
  3. 3Move how-tos into shared skills instead of private chat lore.
  4. 4Create one auditor bot that weekly flags stale skills and checks output destinations.

Approval fence

Stale-skill fixes wait for your yes before rewriting shared skills.

What to tweak

Steal the staleness bot that also checks where output should land.

Source

grovr @grovr_au · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro