Keep · grok-bot SKILL.md
Named Bots, scoped memory, smallest useful roster
WhenUse when one omniscient agent is mixing mail, evals, and outbound in the same memory.
StopNever send external messages without approval. Do not add a specialist until the role is stable. Screens are not a security boundary.
Steps
- Cmd/Ctrl+N → Create new agent. Edit Profile: short name, one primary job, operational description (goal, tools, approval boundary). Cap is 50 Bots + groups combined.
- Description holds rules that stay true (Never send external messages without approval). Thread holds the task (Draft follow-ups for these twelve accounts).
- Start with one Bot that owns an end-to-end outcome. Add a specialist only when the role is stable.
- Working PM roster: Chief of Staff (calendar/Slack/inbox, attention list); Eng mgr who does not code (breaks work, delegates Cloud Agents, checks against the goal); IC eng Bots that spin Cloud Agents; Data analyst on the warehouse who answers in charts; PM sidekick for RFCs from Slack quotes.
- Duplicate a Bot for a new scope (one Account Health Bot per region). Copy keeps profile/skills/routines, not memory or history. Rename and re-scope before work.
- Put Bots in a group only when the handoff itself must be visible. Keep sending/purchasing/deletes behind approval.
LoadCreate new agent. Profile = rules. Thread = task. Cap 50 Bots+groups.
--- name: Named Bots, scoped memory, smallest useful roster description: Use when one omniscient agent is mixing mail, evals, and outbound in the same memory. --- # Named Bots, scoped memory, smallest useful roster When: Use when one omniscient agent is mixing mail, evals, and outbound in the same memory. Stop: Never send external messages without approval. Do not add a specialist until the role is stable. Screens are not a security boundary. 1. Cmd/Ctrl+N → Create new agent. Edit Profile: short name, one primary job, operational description (goal, tools, approval boundary). Cap is 50 Bots + groups combined. 2. Description holds rules that stay true (Never send external messages without approval). Thread holds the task (Draft follow-ups for these twelve accounts). 3. Start with one Bot that owns an end-to-end outcome. Add a specialist only when the role is stable. 4. Working PM roster: Chief of Staff (calendar/Slack/inbox, attention list); Eng mgr who does not code (breaks work, delegates Cloud Agents, checks against the goal); IC eng Bots that spin Cloud Agents; Data analyst on the warehouse who answers in charts; PM sidekick for RFCs from Slack quotes. 5. Duplicate a Bot for a new scope (one Account Health Bot per region). Copy keeps profile/skills/routines, not memory or history. Rename and re-scope before work. 6. Put Bots in a group only when the handoff itself must be visible. Keep sending/purchasing/deletes behind approval. Load: Create new agent. Profile = rules. Thread = task. Cap 50 Bots+groups.