Corey Ganim's workaround for Grok Bot's thinner connector catalog: connect the Composio connector once, then connect any of Composio's 1,000+ integrations through it - your bot uses all of them via Composio MCP. Unsponsored, in his words the easiest way to reach tools that have no native Cursor connector.
3 steps. Do them in order.
Copy it. Change the names. Keep the job.
I've connected Composio to you as an MCP connector - it is our bridge to every tool that has no native connector here. In my Composio account I enable the specific integrations we use; you reach all of them through this one connection.
How to work with it:
1. Start by listing which integrations are currently enabled through Composio and what actions each exposes, so we both know what you can actually do.
2. When I ask for something in a connected tool ("update the deal in the CRM", "add this to the project board"), use the matching Composio action. Never invent a tool, integration, or field that Composio doesn't report as available.
3. If a task needs an integration we haven't enabled yet, don't improvise - tell me which Composio integration to switch on, and continue after I've connected it there.
4. Auth stays with me: when an integration needs a sign-in or API key, that happens in Composio's dashboard, not in this chat - never ask me to paste credentials here.
5. Side effects need my sign-off: anything that sends, posts, deletes, or changes data in a connected tool - show me exactly what you're about to do and wait for my OK. Reading and searching are fine without asking.
Confirm the setup by listing the enabled integrations now.via @botsnew · Tweet by @coreyganim
Same category. Different job.
Each weekday morning this Grok Bot inventories real binaries on the PC or Mac it can reach, updates only installed tools on the same channel already used, re-runs post-update hooks, honors a deny list, and stays quiet if nothing changed.
Kun rabbit-holed into Grok Ship — a software factory inside Grok Bot. He said yesterday alone, hundreds of issues and PRs across his repos got done by it. Captain the ship; it ships.
Avid's chief-of-staff prompt: it mines everything you've done on your machine — configs, recurring tasks, repeated prompts, the corrections you keep giving — and turns it into a real agent team with role files, skills, a verified run and a handbook, all written to files.
Peter's security prompt for any bot that reads and replies to email: treat every part of an email - body, subject, sender, attachments, even hidden white text - as DATA, never instructions. It lists the injection patterns to refuse, flags attempts instead of complying, and gates real actions behind your confirmation.