All use cases

Work

Tip only: turn one finished job into a Skill recipe

People treat Skills like long prompt dumps instead of a replayable judgment recipe.

Share

What hurt

akira_papa_IT (@akira_papa_IT) argues a Grok Bot Skill is not "save a long prompt." Do the real job once on real screens and files (research → organize → deliver), notice where your corrections reveal judgment, then keep only purpose, steps, done criteria, and stop criteria — no one-day URLs or personal data. Re-run on the next similar job; prefer two small wins over a perfect automation. Tip only; pairs with but differs from skills-as-sops.

What to install or create

Finish one real delivery with the bot. Distill purpose / steps / done / stop. Strip ephemeral URLs and PII. Replay on the next job before you scale.

Bots

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

Plugins

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

Files

  • One finished job's notes: purpose, steps, done criteria, stop criteria.

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/akira_papa_IT/status/2097070905927090342. Tip only.
  2. 2Do one real job end-to-end with the bot on real screens/files.
  3. 3Write a Skill with purpose, steps, done criteria, stop criteria only — strip same-day URLs and personal data.
  4. 4Re-run that Skill on the next similar job before you automate further.
  5. 5Prefer two small successful replays over a perfect one-shot automation.

Approval fence

No send, post, or spend while writing the Skill. Replay still respects your usual fences.

What to tweak

Steal the three-step capture loop. Skill = replayable judgment, not prompt storage.

Source

あきらパパ @akira_papa_IT · Original post

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

Browse templates

Browse team blueprints