Bot Generator Bot
A Grok Bot that designs focused Bots, skills and routines, and asks before it builds.
by GetKits
See the difference
Friday review picks the one automation worth building
Before
Bot Generator, Fri 3:00 PM: what did you repeat this week? You: chased 4 freelancers for invoices again, 15 min each. 2 hours on design portfolios, role closes Oct 30. Copied bank payouts into the finance sheet twice, 15 min each.
After
Build Invoice Chaser next: a Grok Bot that drafts overdue-invoice reminders, 48 min/week saved, every reminder held for your approval. Talent Scout scores higher (67 vs 24), but the role closes Oct 30, so it pays back for 3 weeks. Payout Logger (19) waits. All three are now in your Automation backlog in Notion. Decision: build | skip | later
The full Friday review: backlog update and next automation card
Before
Bot Generator (Fri Oct 9, 3:00 PM): 1) What did you do by hand this week that you also did last week? 2) What took longer than it should, and how many minutes? 3) What did you copy from one app into another? You: 1) chased 4 freelancers for invoices again, maybe 15 min each 2) design role shortlist, 2 hours reading 40 portfolios, role closes end of october 3) copied payout totals from the bank into the finance sheet mon and thu, 15 min each
After
BACKLOG UPDATE (Automation backlog) 1. Talent Scout: scores design-role portfolios against your criteria | 96 min/week | Skill | Low | Priority 67 | Idea 2. Invoice Chaser: drafts reminders to freelancers with overdue invoices | 48 min/week | Grok Bot | High | Priority 24 | Idea 3. Payout Logger: copies payout totals into the finance sheet | 24 min/week | Grok Bot | Medium | Priority 19 | Idea NEXT AUTOMATION Job: Invoice Chaser: drafts reminders to freelancers whose invoices are overdue Evidence: 4 chases this week, and you said "again" Time saved: 48 min/week (15 - 3) x 4, estimate Form: Grok Bot Risk: High (sends; every reminder stays a draft until you approve) First build step: /Job interview, starting with where overdue invoices are listed [confirm: sheet or accounting tool] Decision: build | skip | later Why not Talent Scout: it scores higher (67), but the role closes Oct 30, so it pays back for about 3 weeks. Say "build Talent Scout" to do it first, as a Skill. 30-day checks due: none.
Template prep catches a key, an internal link and a customer
Before
/Template prep, Public link. Support Triage description: You are Support Triage. Every weekday at 9:00 AM Europe/Berlin, read new tickets from https://admin.northwind.internal/queue using API key xai-4f9Qk2Lm8... Skill: Escalate. If Dana Ruiz ([email protected]) writes, flag it as VIP. Like last time, file the bug through the tracker MCP server.
After
TEMPLATE PREP Bot: Support Triage Share as: Public link Findings: 1. Secret in Description: "xai-4f" replaced with [confirm: API key in plugin connection] 2. Internal URL in Description: "https:" (admin.northwind.internal) replaced with [your ticket queue] 3. Customer data in Escalate: "Dana R" and her email replaced with [VIP list] 4. Personal setting in Description: "Europe" (Europe/Berlin) replaced with [your time zone] Will not travel: the tracker MCP server; "like last time" relies on your personal memories Recipient must: connect their own ticket source, set their time zone, add their VIP list, connect their own issue tracker Verdict: Share after edits Share steps: Share > Create template > Public link > Copy link Rotate the xai- key now. It was pasted into a chat. Redacted Escalate: If a contact on [VIP list] writes, flag the ticket as VIP. File bugs in [your issue tracker]. If it is not connected, list them for me instead.
Monthly roster review finds a dead Bot and an overlap
Before
Bot roster, Mon Nov 2, 2026: Expense Manager | matches card charges to receipts | 2 routines | last used Oct 30 Metrics Reporter | drafts the Monday metrics post | 1 | Oct 26 Inbox Helper | triages email, drafts replies, tracks invoices, books meetings | 7 | Sep 18 Release Notes Writer | drafts release notes from merged PRs in acme/web | 1 | Oct 29 Changelog Bot | posts a changelog from merged PRs in acme/web | 1 | Oct 15 You: all current
After
ROSTER REVIEW, November 2026 Bot | Job | Routines | Last used | Call Expense Manager | Matches card charges to receipts | 2 | Oct 30 | Keep Metrics Reporter | Drafts the Monday metrics post | 1 | Oct 26 | Keep Inbox Helper | Triage, replies, invoices, meetings | 7 | Sep 18 | Retire: unused 45 days, overloaded (7 routines), four jobs Release Notes Writer | Drafts release notes from merged PRs | 1 | Oct 29 | Keep Changelog Bot | Posts a changelog from merged PRs | 1 | Oct 15 | Merge into Release Notes Writer: same input, similar job This month: 1. Retire Inbox Helper: manage its 7 routines under View conversation details > Routines in that Bot, then I set it Retired in the roster. 2. Merge Changelog Bot: run /Skill from a finished task on its changelog step, paste the result to Release Notes Writer, then retire Changelog Bot. 3. Inbox Helper's reply drafting has no other owner. If you still want it, run /Job interview for a focused Reply Drafter.
What's inside
- bot-generator-bot-setup.md
About this kit
Get a Grok Bot whose only job is building your other Bots: it interviews you about a repetitive job, designs a focused Bot with its skills, routines and test run, audits it for trust, and creates it only after you approve. Every Friday it asks three questions about your week and picks the single best next automation, so your roster grows by one useful Bot at a time. Setup takes about 15 minutes.
What you get
- A complete setup file: the profile (Name, Label and a Description that holds only durable rules), one setup message that saves 5 skills and creates 3 routines, the Notion connection, and a five-part test run with fictional inputs and expected results.
- Five skills, each with when to use, inputs and access, steps, validation, the exact return format and what needs approval:
- Job interview: six questions in one message, the form decision, time saved and priority.
- Bot blueprint: profile, 2 to 4 skills, 1 to 3 routines, plugins and a safe test run for a new focused Bot. It checks your roster for overlap first and creates nothing until you approve.
- Skill from a finished task: turns a task you just did into a reusable skill, keeping your corrections as rules, with the exact message to paste into the Bot that should own it.
- Routine trust audit: scores any routine you paste on 8 checks (approvals, stale data, broad triggers, secrets, retries, test safety) and rewrites it to pass.
- Template prep: scans a Bot for keys, internal URLs, customer data and things a template will not carry, before you share it.
- Three routines: a Friday automation backlog review, a Monday 30-day keep-or-retire check, and a monthly roster review that flags Bots that are unused, overlapping or overloaded.
- A Notion backlog and roster: two small databases with the exact properties to create. Without Notion, the Bot keeps both lists in its conversation.
It uses the same INTERVIEW, FORM DECISION, NEXT AUTOMATION and TRUST AUDIT blocks as the Bot Generator Skill and Dot.
Who it is for
- People who use the Grok Bot app and want three or four Bots that each do one job well, instead of one assistant that does everything badly.
- Operators and founders with a list of "I should automate that" jobs and no time to design each one properly.
- Anyone about to share a Bot as a template with a team or in public.
What it will not do
- It will not create a Bot, save a skill or create a routine without an APPROVAL NEEDED message and your "approve".
- It will not send messages, publish, buy, delete, change production systems or share templates. Sharing stays your action.
- It will not open or edit your other Bots. A new Bot saves its own skills and routines when you paste its setup message.
- It will not design a "General Helper" or a routine that listens to every new message.
- It will not delete rows in Notion or touch any page except its two databases.
- It does not read your mail, chat or code. The Bots it designs get their own plugins, with the narrowest access that works.
Reviews
No reviews yet.
More kits for Bot Builder
Bot Generator Kit
Turn a job you do by hand into a safe, tested AI teammate in under an hour.
Bot Generator Dot
Your dot spots repeat work in Gmail and Slack and drafts the next automation.
Bot Generator Skill
Interview a job, pick Skill, Bot or dot, and generate it with a trust audit.