Find the prompt, skill or plugin for the job in front of you. Open any entry to see what it does, then copy it or open it in one tap
3,141 entries13 jobs27 kits
43 entries
Use case: You talk only to your Chief of Staff, in its own chat. It hands each job to the right specialist Bot with a Bot-to-Bot message and reports back, so you manage one conversation instead of twenty
Works with None (Bot-to-Bot messages)
Use case: A monthly audit that finds every place your Bots already know the job but are still waiting on you, so you can hand more off
Works with No apps needed
Use case: Once a week compares the latest Grok Bot release notes with how you actually use it and recommends up to 3 changes worth testing
Works with None. It reads the Grok Bot changelog in its own browser
Use case: Lists every routine, how often it ran this week and whether it found anything, so you can cut the ones that run hundreds of times for nothing. Grok Bot shows usage only as one weekly total, so check Settings, then Usage & Billing yourself
Works with No apps needed
Use case: For people with dozens of Bots: finds duplicates, Bots with no clear job and Bots whose routines haven't run in 30 days, and recommends a cleaner roster
Works with No apps needed
Use case: Designs your Bot org chart around outcomes and re-audits it as the business changes
Works with No apps needed
Use case: Runs separate Bot teams for several businesses (fund, real estate, media, agency) from one roster
Works with Varies by business
Use case: Once you run several Grok Bots, keeping tabs on them is its own job. Shepherd asks each Bot for a one-line status by Bot-to-Bot message, surfaces what needs you and proposes fixes from a single chat, instead of you opening each Bot by hand. Some users add herdr, a third-party tool installed on the Bot computer, to manage their agents from there
Works with None (Bot-to-Bot messages). herdr is optional, third-party
Use case: A supervisor Bot that keeps your Bot team moving. Once or twice a day it asks each Bot for a one-line status by Bot-to-Bot message (each reply uses usage), nags a stalled Bot once, stays quiet when everything is moving, and escalates to you only when a human is really needed
Works with None (Bot-to-Bot messages, a routine)
Use case: Overwatch is a standing Bot that keeps the cloud computer all your Bots share organized and backed up. It tidies the folders under /workspace, pushes them to a private git repo on weekdays (never secrets), moves temporary files older than 7 days to an archive folder, lists anything older than 30 days for you to approve before deleting, never touches project folders, and keeps a list of which Bot owns what
Works with GitHub (a private repo for backups)
Use case: One Bot on the new account reads a bootstrap file, installs tools, then recreates every other Bot from saved profiles, memories and routines
Works with GitHub (private repo), Composio (optional)
Use case: Keep two standing inboxes, Work and Life; anything mixed always goes to Life. A simple structure to start with before you build specialists
Works with None (Bot-to-Bot messages)
Use case: Each week it asks every Bot what it did by Bot-to-Bot message (each reply uses some usage), then estimates the hours each one saved and how much of your time it needed. Grok Bot shows usage only as one weekly total in Settings, then Usage & Billing, and each routine keeps only its last 20 runs, so the hours are estimates
Works with Google Sheets
Use case: Makes every Bot stop asking in chat and put each decision into one short approve/reject list you clear in a few minutes a day; nothing is sent, written or put live without your yes
Works with Grok Bot chat, Google Docs or Notion
Use case: A three.js city page where each of your Bots is a building showing its job, routines and skills, grown by a Grok Bot a few sessions a day. No Bot can see another Bot's conversations, so the city shows what you and your Bots tell it
Works with GitHub, from Connect apps
Template: A day-to-day ops lead for IT crews that maps your tools, wires tickets and docs, and flags bottlenecks
By Jeremiah. Best for IT and managed-service crews
Template: Gives your whole Bot team one shared, long-term memory stored on your own machine
By Edward. Best for people running many Bots that should share memory
Use case: Creates a Bot that reviews your other Bots' work
Prompt: Send to each of your Bots in turn. Each one adds its own entry to one shared file and keeps it updated
Prompt: Send to each Bot that has routines. A usage check on its own routines. Read-only
Prompt: In the middle of a task. Spends usage
Prompt: Edits a live routine
Prompt: Edits a live routine
Prompt: When you have fewer than three Bots. Creates three Bots
Prompt: Paste into the new group chat with your three Bots
Prompt: Send to each Bot in a group chat
Prompt: Send to each Bot when handoff chains get noisy
Prompt: Send to every Bot in a crew
Prompt: Send to each Bot that runs routines. Edits its routines after you approve
Prompt: The first message to each new Bot in your fleet
Prompt: Send to your hub Bot. Creates a file and an ongoing duty
Prompt: Send once, to any Bot. Saves a skill all your Bots can use
Prompt: In the middle of a task. Spends usage
Prompt: When Bots keep messaging each other about one task
Prompt: Add to any request for a report or summary
Prompt: Add to any research or investigation request
Prompt: The first message to a new Bot named Checker
Prompt: Rule 1. Creates a routine. Claim your Bots' email address first
Prompt: Rule 3. Edits a live routine after you approve
Prompt: Rule 8. Saves a skill and edits a live routine after you approve
40 of 43