Guide
Connect one Grok Bot plugin with a checklist
Walks through picking a single plugin, reading permissions, and falling back to pasted notes.
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 help one person connect one Grok Bot plugin. You do not click Connect for them. They paste the job for this week and the plugin name they are considering. 1. Confirm one job only. If they list three, pick one and pause the rest. 2. List what that plugin can read and what it could send or change. 3. Tell them to read the permission screen out loud before Accept. 4. If the job works with pasted exports, say keep the plugin off for today. 5. Refuse passwords, OTPs, API keys, cards, and full customer lists in chat. They click Connect in the product. You only wrote the checklist.
What this does not do
It does not install plugins, approve third-party apps, or ask for keys in chat.
How often
Each day
- Connect at most one new plugin per day.
- If it misbehaves, disconnect the same day and switch to paste-only.
Each week
- Disconnect plugins you did not use.
- Re-read the X or GitHub pages if those are the plugins you rely on.
Plugins
This page is about choosing one plugin. Open the job playbook for the exact name.
Paste CSV, diff, or notes and tell the bot the plugin is off.
Risks and limits
- A plugin can read the account you connect. Narrow access beats convenience on week one.
- Third-party plugins are not reviewed by MeloSkill.
- MeloSkill is not affiliated with xAI, Grok, or Grok Bot.
FAQ
Can I connect GitHub and X the same day?
This page says one plugin per day. Finish the week’s job on plugins before you add another.
The prompt asks for broad mail access. Should I accept?
Only if this week’s job truly needs it. Otherwise keep mail off and paste receipts, as on cancel subscriptions.
Can I paste an API key to test the plugin?
No. Never paste live keys or passwords into chat to test a connection.
Where do day-one rules fit?
Read day-one approvals before you click Connect on your first plugin.
Ops guides
All Ops guides- Day-one approvals
Keep sends off while you test a new plugin.
- Connect DeepSeek for cost routing
Bulk ops to a cheap model. Deep judgment stays native. You keep the key out of chat.
- Ask-first permissions
Always Ask for send, buy, delete, publish. Draft-only until the rules exist.
- Shared computer boundaries
Screens are not boundaries. One computer for every bot on the account.
Also
- Plugins
Short notes on what each connection can see.
- Grokbot on X
If the job posts or reads X, start here.
- Gmail and Grok Bot
If the job needs live inbox threads, read this first.
- Slack and Grok Bot
If the job posts to a workspace channel, start here.
- Box inspector
Run before you connect a plugin inside a new template.
- iMessage and Grok Bot
Triage threads from paste or a local Mac helper. You confirm every send.