All use cases

Engineering

Same steps every time? Keep a skill — not another bot

Every new idea spun up a bot — most of them did not need a seat.

Share

What hurt

Jerry Dai (@shuntian2026) Day 2: with one front-door bot (Aria), he asked five real jobs the same question — same steps every time → skill (recipe); needs its own files/memory across tasks → bot (seat). Three of five stayed skills he can pause and resume; two deserved bots. Not affiliated with xAI.

What to install or create

Run your backlog through skill-vs-bot. Pause skills instead of deleting; hire bots only for owned memory.

Bots

  • Front door

    Routes work. Does not do every job itself.

Plugins

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

Files

  • skills/. Paused recipes you can turn back on.

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/shuntian2026/status/2109642284157583757 (credit @shuntian2026).
  2. 2List five real recurring jobs.
  3. 3For each: same steps every time → write/keep a skill; needs owned memory → keep or hire a bot.
  4. 4Pause skills you are not running; do not delete the recipe file.
  5. 5Refuse new bot hires that fail the memory test.

Approval fence

Do not create new bots while the five-job test is unfinished.

What to tweak

Steal the one question. Recipes scale; seats are expensive.

Source

Jerry Dai| 顺天 @shuntian2026 · Original post

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

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro