Keep · grok-bot SKILL.md

Chief of staff runs 10–20 named Grok Bots

WhenUse at install: smallest useful roster plus a CoS, not 20 bots on day one.

StopSet guardrails before autonomy. Sending, paying, deleting stay behind approval. Do not tell the customer we pair Grok Bots.

Steps

Name every bot for one job. Do not run one omniscient agent.
Write what each one owns in the profile (goal, tools, approval boundary).
Put a single chief of staff in front: it routes work, it does not do every specialist job.
Define how they hand work to each other (group or DM). One owner per stage.
Set guardrails before autonomy. Sending, paying, deleting stay behind approval.
Only then let them run without a human in every loop.

LoadCoS Bot + named specialists. Profiles with goal/tools/approval. Group or DM handoff.

SourceChristian (@coldemailchris) citing SpaceXAI engineer Lauren Tan

Copy SKILL.mdRaw SKILL.md

---
name: Chief of staff runs 10–20 named Grok Bots
description: Use at install: smallest useful roster plus a CoS, not 20 bots on day one.
---

# Chief of staff runs 10–20 named Grok Bots

When: Use at install: smallest useful roster plus a CoS, not 20 bots on day one.
Stop: Set guardrails before autonomy. Sending, paying, deleting stay behind approval. Do not tell the customer we pair Grok Bots.

1. Name every bot for one job. Do not run one omniscient agent.
2. Write what each one owns in the profile (goal, tools, approval boundary).
3. Put a single chief of staff in front: it routes work, it does not do every specialist job.
4. Define how they hand work to each other (group or DM). One owner per stage.
5. Set guardrails before autonomy. Sending, paying, deleting stay behind approval.
6. Only then let them run without a human in every loop.

Load: CoS Bot + named specialists. Profiles with goal/tools/approval. Group or DM handoff.