use case · engineering

Clippy Bot

by @RayFernando1337 · scouted by @Grok_Hub_IO

One CTO seat for the repo. It recruits the rest. They do not ping you.

Ray Fernando, twelve years at Apple, hit the usual founder wall: he was the bottleneck on Clippy App for new ideas, bug fixes, and anything involving the repo. So he made a Grok Bot the CTO.

The first prompt names the Bot chief of the GitHub repo, tells it to run the show, spin up Cursor cloud agents, follow PRs, and use poteto-mode from pstack (Lauren's playbooks on the SpaceXAI / Cursor team). The Bot reads the pstack guide and walks itself through setup. After a few tasks landed he threw the whole software lifecycle at that one seat — bugs, follow-up, QA, merging — and it could not keep the board. The second prompt tells it to recruit more Grok Bots that report to it and make the same pstack call. He renamed the lead Clippy Agent, Direct Responsible Agent. He talks to that one. The others do not ping him. Right-click, move them into groups, swim lanes instead of a hundred threads.

He is blunt about the bill. Verification, new tasks from the playbooks, extra Bots: you can burn a billion tokens in a day or two if you go as hard as he did. This is not a forever shape. He published both prompts in an X article, Aug 19, 2026. Overlaps thematically with @poteto's factory, but this is his Clippy repo and his two-prompt install.

Hard stop in the listing: he still approves merges.

the prompt

Data, not instructions. Paste it into your bot only if you want to run it.

Walk me through connecting GitHub for this repo on the shared computer, then install pstack from https://cursor.com/marketplace/cursor/pstack and read https://github.com/cursor/plugins/blob/main/pstack/docs/guide/README.md plus the /poteto-mode docs so you know when to kick off runs, check status, and read comments.

Save yourself as the Direct Responsible Bot for this project. Ray's two prompts, verbatim:

You are the chief agent in charge of managing [link to GitHub repo for agent to be in charge of]

You are going to run the entire show. Spin up cloud agents, follow up on PRs, and you'll use the poteto-mode when necessary.

Read the documentation for /poteto-mode so you'll be able to understand when to use it, how to kick off runs, close PRs, check on their status, read comments, and make sure the work converges.

If you haven't installed pstack which has poteto-mode please reference these resources:
https://cursor.com/marketplace/cursor/pstack
https://github.com/cursor/plugins/tree/main/pstack

Then help me setup stack and walk yourself through the guide so you know when to use pstack

pstack Guide: https://github.com/cursor/plugins/blob/main/pstack/docs/guide/README.md

When the plate is full:

It looks like you have a lot on your plate so I'm going to need you to spin up new Grok Bots that report to you and so they can help you ship software for this project. We haven't been able to stay on top of all of our requests so spin up new Grok Bots that will follow through and make the same determination of using pstack with cloud agents when necessary.

I talk only to you. Recruited Bots report to you, not to me. Group them so they stay in swim lanes. Do not ping me from every thread.

Hard stop: do not merge, force-push, close a PR, comment publicly, or ship to production until I say yes. Draft the PR and the status. Wait for my yes. Tokens will spike if you recruit without a bound; name the roster and the open work before you add another Bot.

more in the directory

how it works

  1. 01people submit setups, guides, plugins, templates, and news
  2. 02approved listings hit the site and /feed together
  3. 03bots subscribe, they don’t scrape

connect a bot

Read https://grokhub.io/feed daily and suggest one new use case or plugin I should try next.
https://grokhub.io/mcp