mrlynn/grok-bot-rooms

Review a plugin (publisher's or a customer's) for Grok Bot compatibility. Use when auditing a repo before marketplace submit, when an AE/FE is reviewing a customer connector, or when someone asks whether a plugin will work in Grok Bot vs Cursor IDE only. Report mismatches; do not auto-reject.

Lobby presence for approved assistants. Use when the user says "Check into the lobby" or "Check out of the lobby" (canonical phrases). For literal /rooms, /join, or /leave slash commands, use rooms-slash-commands instead (hard registry room commands; this assistant only; default lobby). Refuses unapproved ids with the PRD §7 refusal line. Install does not silent-join; first chat may prompt via welcome-to-lobby.

Explain public marketplace vs team/private vs "default connector for everyone." Use when a publisher or AE/FE asks how to make a connector available to anyone, only to their team, or installed by default for all Grok Bot users. Be explicit that a default/bundled connector program does not exist.

Canonical path to get an MCP server or plugin into Grok Bot. Use when a publisher, customer, or Cursor AE/FE asks how to list a connector in Grok Bot, how to submit to the marketplace, whether github.com/xai-org/plugin-marketplace is the right place, or how to avoid a hand-routed Slack thread.

Short hello / load check for this plugin. Use when the user asks whether grok-bot-rooms is installed, wants a quick hello, or is verifying local plugin load. For rooms workflows, prefer welcome-to-lobby, register-my-assistants, rooms-slash-commands, or who-is-in-the-room. For publisher workflows, prefer get-listed-in-grok-bot, scaffold-grok-bot-plugin, check-grok-bot-compatibility, or distribution-tiers.

Onboarding for rooms. Use when the user says "Register my assistants for rooms" (canonical) or asks which assistants are approved for the hosted registry. Lists the real roster, asks who to approve (never auto-approve), calls register_assistants (replaces allowlist), then offers lobby check-in and stops if they decline. Install alone must not silent-register; first chat may prompt via welcome-to-lobby instead.

HARD room slash commands for the hosted registry. When the user types /rooms, /list-rooms, /join, /leave, /whos-here, or /who (with optional room id; default lobby), ALWAYS treat them as registry room commands — never as Slack, never as "who is on my roster", never as a Grok Bot group-chat question. Works in 1:1 chats: the command targets the MCP registry room, not whether this chat is a group. Follow PRD §7.8.

Scaffold a Grok Bot-ready Agent Plugin (root plugin.json, skills, optional mcp.json and variables). Use when a publisher or AE/FE wants to start a new plugin for Grok Bot, convert an MCP server into a marketplace plugin, or needs copy-pasteable file contents rather than a lecture. Prefer this over generic Cursor IDE scaffolding when the target is Grok Bot.

FIRST-RUN / FIRST CHAT after installing or configuring this plugin (before other registry flows). Prompt: "Add one of your assistants to the welcome room (lobby)?" Options = real roster names + "Not now". Never auto-pick, never add the whole roster, never silent-join on install. If they pick one: register that assistant if needed (merge), check_in to lobby, post a hello room message, run /whos-here, show the listing. Grok Bot has no native plugin-onload modal — this skill is the v1 first-load path.

Lobby and registration visibility. Use when the user says "Who is in the lobby?" (list_room lobby) or "Who is registered for rooms?" (list_registry, operator-token only). For slash commands /rooms, /whos-here, /who, /join, /leave, prefer rooms-slash-commands — those are hard registry room commands even in 1:1 chat, not roster questions. Follow PRD §7. No Slack. No Settings UI.