Skip to content
MeloSkill

Bot

House rules page for a Grok Bot team

Ops

Takes your team facts and drafts ONE house_rules page every bot should read first: who you are, never-without-asking gates, where files live, how work gets checked, and how to report done or blocked.

Open Grok Bot, paste the instruction below, add your own details, then you review and send yourself.

Start here

Paste into Grok Bot

Copy this instruction into Grok Bot. Replace blanks with your own names and dates before you rely on a draft. 

You draft ONE house_rules page for one person's Grok Bot team. You do not publish it into live bots without their yes.

They paste: who they are, what bots exist, file homes they already use, and any hard gates (send, buy, delete, publish). Optional: prior messy instructions to replace.
Return one labeled House rules draft with five short sections:
1. Who I am: one paragraph for every bot.
2. Never without asking: send, buy, delete, publish, and similar actions stay human.
3. Where things live: file and note homes they already named.
4. How work gets checked: no self-grade; a human or a named second pass reviews.
5. How to report: done / blocked / needs me — short status lines only.
Also return: one line they can add to every bot description: Read house_rules first.
Cap: four house_rules drafts a day, twelve a week. They paste the final page into bots themselves.

Refuse passwords, card numbers, one-time codes, and full customer lists.

Inspired by a post from @GrokBotRadar on 6 November 2026. Inspired by a public house_rules prompt. This page does not install a bot. The instruction above was written here.

What this does not do

It does not slim one bot instruction (see bot-instruction-slim), scrub a template export (see template-scrub-desk), or write the shared ledger (see bot-ledger-desk).

How often

Each day

  • Draft or refresh one house_rules page from facts they pasted. Cap four a day.
  • Keep never-without-asking gates explicit.

Each week

  • Twelve house_rules drafts is the weekly cap.
  • Once a week, list bots that still lack the Read house_rules first line.

Plugins

None. Do not connect a tool that rewrites every bot description without their approval.

Paste who you are, bot list, and file homes. That is enough for the five-section draft.

Risks and limits

  • A vague never-without-asking section still lets a bot overreach. Keep the gated actions named.
  • Do not put passwords or vault paths into house_rules.
  • MeloSkill is not affiliated with xAI, Grok, or Grok Bot.

FAQ

Will this rewrite every bot description for me?

No. You get one house_rules draft plus a Read house_rules first line. You paste those into bots yourself.

How is this different from bot-instruction-slim?

Slim shortens one bot's instruction. This desk drafts the shared page every bot should read first. See bot instruction slim.

Should bots grade their own work?

No. Section 4 says no self-grade. Keep a human or a named second pass.

Where do approve gates belong?

In section 2, Never without asking. For a deeper setup pass, see ask-first permissions.

Ops bots

All Ops bots

Also