Decide · grok-bot SKILL.md

Loops: Grok Bot as outer loop that fires Cursor cloud agents

WhenUse when the manager Bot should not do the compute.

StopOuter loop never commits/pushes unless the charter says wait-for-go. Managers don't heavy-lift.

Steps

Create one Bot. Name is optional (does not change behavior). Title = short job. Description = operating instructions.
Keep brainstorming, dead ends, Slack/Notion/Figma search in this Bot.
Once the problem is a clear code change, hand the repo to a new Cursor Cloud Agent (or Grok Build CLI) with a clean /goal-style prompt and testable proof.
If the task is already a clear code change, skip Grok Bot and send it to the coding agent directly.
Treat the shared cloud computer as one trust zone — extra Bots are not a security boundary.

LoadGrok Bot outer loop. Cursor cloud agents. File handoff.

SourceMatt Palmer (Cursor / SpaceXAI; “Chat is all you need” 2026-08-18; Loops template 2026-08-28)

---
name: Loops: Grok Bot as outer loop that fires Cursor cloud agents
description: Use when the manager Bot should not do the compute.
---

# Loops: Grok Bot as outer loop that fires Cursor cloud agents

When: Use when the manager Bot should not do the compute.
Stop: Outer loop never commits/pushes unless the charter says wait-for-go. Managers don't heavy-lift.

1. Create one Bot. Name is optional (does not change behavior). Title = short job. Description = operating instructions.
2. Keep brainstorming, dead ends, Slack/Notion/Figma search in this Bot.
3. Once the problem is a clear code change, hand the repo to a new Cursor Cloud Agent (or Grok Build CLI) with a clean /goal-style prompt and testable proof.
4. If the task is already a clear code change, skip Grok Bot and send it to the coding agent directly.
5. Treat the shared cloud computer as one trust zone — extra Bots are not a security boundary.

Load: Grok Bot outer loop. Cursor cloud agents. File handoff.