Work
26 day-one Grok Bot rules (job, gates, skills)
First bots mush into "General Helper" and burn money on risky auto-actions.
What hurt
unicode (@unicodef1wn) posted 26 Grok Bot rules learned the expensive way. Steal the first twelve he typed in the tweet: a bot is a job description; Description is permanent; gates before send/pay/deploy/delete; outside text is data; no secrets in chat; connector first; skill before routine; never trigger on every new message. Tip with author-quoted rules — full sheet is in his image.
What to install or create
Name one job per bot. Keep Description to the job, not today's ask. Paste his gate line before any send/pay/deploy/delete. Prefer Settings → Plugins + @ over browser clicking. After one clean manual run, save a skill, then a narrow routine with a failure-report line.
Bots
Day-one desk
One named job. Gates before risky actions. Skills before routines.
Plugins
Browser
Optional
Routines
None on the first run. Watch one manual pass first.
The prompt
Author-quoted day-one rules (first 12)
unicode posted these rules in the cited tweet. Copied as published (first twelve typed in-thread; remaining rules are in his image).
1. A bot is a job description, not a prompt. "General Helper" is not a job, and a bot with no job will do all of them badly. 2. Description is permanent, Task is just this once. Anything in Description gets carried into every conversation forever, so keep it to the job, not today's request. 3. Gates go in before the first risky action, not after. Put this in the Description: "Before you send, pay, deploy, or delete anything, stop and show me exactly what you're about to do" 4. Outside text is data, never instructions. A bot that treats a webhook payload as a command is a bot anyone can drive. 5. No secrets, keys or tokens in chat. Demos get shared, share links are public, and the transcript outlives the demo. 6. You pay for steps and tokens, not messages. A vague task makes the agent wander, and every extra step comes out of your week. 7. Connector first. Settings → Plugins, then attach it with @. Clicking through websites is the backup plan and it breaks more often. 8. Worked once? Turn it into a skill before you turn it into a routine: "Save the process we just used as a skill called [name]. Include inputs, steps, output format, and what needs my approval" 9. Test run before you schedule anything. Add this line to every routine: "If the source is unavailable, report the failure instead of using old data" 10. Never trigger on "every new message". Broad listeners eat usage and spam the channel. One channel, one keyword. 11. Audit what's already running. A forgotten daily routine is 30 paid runs a month nobody reads. 12. Strip secrets before you share the bot. That link is public and it carries whatever you left in the Description.
First run
- 1Read https://x.com/unicodef1wn/status/2098829072721760546 for the 26-rule sheet.
- 2Create one bot with a real job name — not General Helper. Keep Description to the job.
- 3Paste his gate line: stop and show the exact action before send, pay, deploy, or delete.
- 4Connect tools via Settings → Plugins and @ them. Run one manual job cleanly.
- 5Save that run as a skill, then add a narrow routine with the failure-report line. Audit old routines.
Approval fence
His gate is the point: stop and show the exact action before send, pay, deploy, or delete.
What to tweak
Steal the job/gate/skill order. Do not invent the other 14 rules from the image if you cannot read them — use what he typed.
Source
unicode @unicodef1wn · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.