Bot Generator Bot
A Grok Bot that designs focused Bots, skills and routines, and asks before it builds.
GetKits 제작
차이를 직접 확인하세요
Friday review picks the one automation worth building
사용 전
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.
사용 후
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
Support Reporter designed, audited and held for approval
사용 전
Fri Nov 6, 2:40 PM /Bot blueprint for this one: INTERVIEW Job: Support Reporter: drafts the Monday summary of last week's tickets for #support-leads Inputs: ticket CSV in Drive Support/Exports, lands Mondays by 7:30 AM, fresh if its tickets are dated last Monday to Sunday Tools: Google Drive: read Support/Exports; Slack: write, one post in #support-leads Good output: 5 lines: volume, top 3 tags, oldest open ticket, one risk with an owner Never: send (no post without my OK); name customers; delete How often: weekly, Monday 8:00 AM America/New_York, 40 minutes by hand Open: none
사용 후
Support Reporter is ready to create: 1 Bot, 2 skills, 1 routine, 16/16, 32 min/week saved, first run Mon Nov 9. Roster check: no Active Bot reads Support/Exports. BLUEPRINT (excerpt) PROFILE Name: Support Reporter Label: Monday support summary Description: You are Support Reporter. Your job: every Monday, draft the summary of last week's tickets for #support-leads. Ask before: posting in #support-leads. Show the exact post and wait for "approve". Never: post anywhere else, email anyone, name a customer or delete anything. Use ticket IDs and tags. When the export is missing or stale, report the failure instead of using old data. Unknown facts are [confirm]. Tone: numbers first, five lines. SKILL: Ticket summary; SKILL: Risk call-out ROUTINE: Monday support summary Owning Bot: Support Reporter Schedule and time zone: every Monday at 8:00 AM, America/New_York Input source: the CSV in Drive Support/Exports with tickets dated last Monday to Sunday Runs skill: /Ticket summary, then /Risk call-out Expected result: one 5-line draft here, with an APPROVAL NEEDED to post it Approval boundary: one post per approve, run key support-summary-<ISO week>; nothing else is sent If a source is missing or stale: no CSV with last week's tickets means ROUTINE FAILED. Report the failure instead of using old data. PLUGINS @Google Drive [confirm: name in Marketplace]: read Support/Exports only @Slack [confirm: name in Marketplace]: post in #support-leads only, after approve EVENT TRIGGERS: none TEST RUN Safe input: "next run only: Support/Exports TEST and the private #support-test" Run: View conversation details > Routines > Monday support summary > Test run Check: 5 lines match your count; a rerun drafts nothing new; an empty TEST folder gives ROUTINE FAILED TRUST AUDIT Artifact: Support Reporter (Grok Bot) Specific job: PASS - one summary, one channel Approval boundaries: PASS - the post waits for approve Missing or stale data: PASS - tickets must be dated last week Narrow triggers: PASS - Monday 8:00 AM America/New_York No secrets or private data: PASS - ticket IDs and tags only Safe retries: PASS - run key per ISO week Safe test run: PASS - TEST copies, rerun, broken source Output destination: PASS - one draft here, then #support-leads Score: 16/16 Verdict: Ship Fixes: none APPROVAL NEEDED Action: Create 1 Bot Target: Support Reporter Content: the PROFILE above If you skip: nothing is created; the backlog row stays Interviewed Reply: approve | edit <what> | skip
Template prep catches a key, an internal link and a customer
사용 전
/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.
사용 후
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
사용 전
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
사용 후
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.
구성
- bot-generator-bot-setup.md
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.
리뷰
아직 리뷰가 없어요.
Bot 빌더 Kit 더 보기
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.