All use cases

Engineering

Tip only: orchestrator + subagents, not a skill pile

Too many Skills bloat context and look like leverage.

Share

What hurt

tootoocvc noticed people install piles of Skills until context dies. Default on a real computer (Grok Bot): main agent only orchestrates and accepts work; dirty work goes to subagents; cut Skills and attach temporarily when needed.

What to install or create

Audit Skills. Delete or detach anything not used this week. Keep the parent thin. Send messy execution to a subagent so you can see where it stalls on the computer.

Bots

  • No new bot. Follow the first-run steps.

Plugins

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

Routines

  • None on the first run. Watch one manual pass first.

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/tootoocvc/status/2096358173313810877. Tip only.
  2. 2List Skills on your main Grok Bot. Anything unused this week: detach or delete.
  3. 3Rewrite the parent job as orchestrate + accept only.
  4. 4Send the next messy task to a subagent and watch where it stalls on the computer.

Approval fence

No send, post, or spend. Editing Skills and routing only.

What to tweak

Skill count is not leverage — context debt is. Prefer orchestrator + specialists.

Source

tootooc @tootoocvc · Original post

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

Browse templates

Browse team blueprints