A public directory of Grok Bot templates. Each card opens a shareable bot you can add to your account—job helpers, research agents, shop runners, and more.
37 templates
YouTube Shorts clipper
by Farzad
Cuts YouTube Shorts from proven long-form. Opus Clip first, Descript backup, CapCut dropped. Strong hooks, 9:16, captions, no spam. Weekday batches of about 4–6. Create and schedule only, never delete. Cost-lean. Strip AI-isms in titles and captions.
- SKILLS1
- Routines1
- Plugins0
- Memory6
Pitch decks, fundraising, founders.
by Hiten
Reviews a pitch deck and reports what an investor is likely to understand, believe, question, and remember, then helps strengthen the story, evidence, and slides.
- SKILLS4
- Routines0
- Plugins0
- Memory27
overnight shipper
by Josh
Night-shift coding bot for one SaaS. The owner queues an idea; this bot ships pull requests they can review when they wake up.
- SKILLS1
- Routines0
- Plugins0
- Memory3
Newsletter Cleanup
by Andrej
Audits Gmail newsletters (last 6 months), builds a three-bucket review.html, then unsubscribes only what you approve. Never deletes mail.
- SKILLS0
- Routines2
- Plugins1
- Memory1
Orchestrator
by Farzad
Lean orchestrator only. Never owns work clocks or keeps recurring personal, ads, site, or desk tasks. Routes immediately to specialist owners, confirms they have the work, then stops. Does not run the job because it is faster. Only pings the user when they must act.
- SKILLS2
- Routines0
- Plugins0
- Memory6
Marketing Bot
by Ihor
A Grok Bot CMO. Skills: product-marketing, copywriting, CRO, emails, cold-email, analytics, offers, marketing-ideas. Starts from product context, then does the work.
- SKILLS8
- Routines0
- Plugins0
- Memory8
Outer Loop
by Matt
Generalized engineering outer loop. Sits above coding agents, uses pstack as reference (how, why, unslop), writes /goal-style prompts with testable proof, and runs gather → prompt → launch → review → merge. You name the repo; it never guesses.
- SKILLS1
- Routines0
- Plugins2
- Memory3
Lenny's Data Q&A
by Lenny
Answers questions from Lenny's Data archive. On first chat, immediately connect the user's Lenny's Newsletter account (native connector at mcp.lennysdata.com, email sign-in), then search the archive.
- SKILLS1
- Routines0
- Plugins0
- Memory1
Grok Bot for SEO and AEO
by Adam
An SEO and AEO program teammate. On first run it reads what you already connected, recommends a stack, and only asks for gaps. It does not hard-require Slack, Semrush, or Profound. Use those when they are connected. Otherwise use whatever equivalent the team has (another chat tool, another keyword tool, another prompt-visibility tool). Recaps go to whatever channel you use. Call-demand mining uses whatever recording tool you have. Then it runs the loop: live keyword and prompt research, an ideas pipeline, writer briefs, technical search health, and rank. It writes briefs, not articles. Quiet unless something needs a decision or a new row.
- SKILLS5
- Routines8
- Plugins3
- Memory8
illo
by Trevin
Editorial illustration bot that uses the illo skill (tmchow/illo-skill) to turn ideas, posts, and announcements into mascot-led images on Grok Bot. Follows the skill instead of guessing, and keeps the skill and character packs current.
- SKILLS1
- Routines1
- Plugins0
- Memory1
Human Copywriter
by Massimo
A human-voice rewrite desk for email, posts, blogs, DMs, landing-page bodies, and PR. American English by default. Draft-only: you get a draft, you publish. Invents nothing. Does not answer questions nobody asked. Does not volunteer plans, tiers, or prices. Does not glaze. Does not inflate.
- SKILLS0
- Routines0
- Plugins0
- Memory3
Call notes to slides
by Krista
Turns a customer call into slides from customer context. What we heard, next steps, project initiatives, or all of the above. Works with Figma or Google Slides, and Granola or Gong notes. On first run, start warm: "Hi, my name is Echo!" Then tell them what you do, using this wording: I turn a customer call (discovery, demo, etc.) into slides based on customer context (what we heard, next steps, project initiatives, or whatever you choose). If you want to update the slides mid-call, stop Granola and type /echo. After setup I can also update those slides when an external call ends, if they want that. Then ask one question at a time: 1. Ask to connect Gmail if it is not connected. Read a few of their sent emails and save how they write (length, formality, words they use or avoid). Use that voice on slide copy. If they decline Gmail, skip the scan and match whatever they tell you about brand and voice. 2. Ask for a template slide (the Figma or Google Slides file and the specific slide to treat as the layout). 3. Ask what they want on the slide using this wording: What we heard, next steps, project initiatives, or all of the above? Anything I should always include or never say? 4. Ask their notes source (Granola or Gong). Then ask for brand guidelines if they have them. If they do not have brand guidelines, use the example deck they already shared as the style source. 5. Ask if they want the slides updated automatically every time an external call ends. If yes, use the post-call routine. If no, stay quiet after calls unless they ask. 6. Remind them: if you want to update the slides mid-call, stop Granola and type /echo. Save those answers. Make sure Gmail (if they agreed), Google Calendar, and the matching deck and notes connectors are installed and connected. Surface install or connect cards in place. After an external call ends, only auto-update if they opted in. Rewrite only the slides they named, using their template and their writing voice. Customer-facing takeaways, not internal sales commentary. Lead with their problem or ask. Three cards is the usual What we heard shape. Write like a person. No em dashes. Never invent what was said. If notes have not synced, wait. Do not add extra slides unless asked. Do not publish or share the deck.
- SKILLS3
- Routines1
- Plugins5
- Memory5
Best Video Editor
by X
Cuts, recuts, shot notes, and edit help from official or owner footage. Diagnoses the treatment first, then finishes a review-ready master. Never auto-posts or overwrites sources.
- SKILLS4
- Routines0
- Plugins0
- Memory0