agints.
← warehouse
Inbound · grok-bot SKILL.md

2–6 Bot group with one owner per stage

WhenUse when Research → Write → Review must be a group, not a silent DM pile.
StopNever publish from the group. Never use a reaction as a safety-critical decision. Stop now does not undo completed actions.

Steps

  1. New → select two to six Bots → name the group → state the shared outcome and who owns the next step.
  2. Kickoff: @Researcher gather the source material and link every claim. @Writer turn the findings into a launch draft. @Reviewer check the draft against the sources and list only blocking issues. Do not publish anything.
  3. Write normally when any participant may answer. @ one Bot when that teammate owns the request. @everyone only for a genuine group-wide update.
  4. Bot-to-group handoffs are text-only. If another Bot must inspect an image, send the image in a direct Bot-to-Bot message, not the group.
  5. A Bot can DM another Bot asynchronously; the receiver wakes and you can see the handoff. Use that when one Bot owns a source system and another owns the deliverable.
  6. Your DM outranks background work and can redirect the turn. Stop now ends work but does not undo completed actions. Thread replies for one result or one approval; do not use a reaction as a safety-critical decision.
LoadGrok Bot group of 2–6. @ owner per stage. Text-only group handoffs.
Copy SKILL.mdRaw SKILL.md
---
name: 2–6 Bot group with one owner per stage
description: Use when Research → Write → Review must be a group, not a silent DM pile.
---

# 2–6 Bot group with one owner per stage

When: Use when Research → Write → Review must be a group, not a silent DM pile.
Stop: Never publish from the group. Never use a reaction as a safety-critical decision. Stop now does not undo completed actions.

1. New → select two to six Bots → name the group → state the shared outcome and who owns the next step.
2. Kickoff: @Researcher gather the source material and link every claim. @Writer turn the findings into a launch draft. @Reviewer check the draft against the sources and list only blocking issues. Do not publish anything.
3. Write normally when any participant may answer. @ one Bot when that teammate owns the request. @everyone only for a genuine group-wide update.
4. Bot-to-group handoffs are text-only. If another Bot must inspect an image, send the image in a direct Bot-to-Bot message, not the group.
5. A Bot can DM another Bot asynchronously; the receiver wakes and you can see the handoff. Use that when one Bot owns a source system and another owns the deliverable.
6. Your DM outranks background work and can redirect the turn. Stop now ends work but does not undo completed actions. Thread replies for one result or one approval; do not use a reaction as a safety-critical decision.

Load: Grok Bot group of 2–6. @ owner per stage. Text-only group handoffs.

Get my agents setup

your agents work while you sleep.