把 38 个例程按 8 类触发器塞进一个 Grok Bot
作者展示用 webhook、每小时、每日、Slack、GitHub、邮件、夜间和周一审计八组触发器组织 38 个 Grok Bot 例程,并附可粘贴的提示词。
THIS IS A F*CKING 38-JOB COMPANY INSIDE ONE GROK BOT someone finally organized AI automation like an actual business instead of a bunch of agents running around with no purpose. 38 routines. 8 trigger groups. one bot. and every job has its own reason to wake up. the setup is surprisingly clean: → WEBHOOK runs 7 jobs for deployments, payments, orders, refunds and incoming leads → HOURLY + CHECK handles 6 monitors covering prices, repository changes, inbox counts and competitor pages → DAILY 08:00 delivers 5 scheduled tasks for morning briefs, metrics, calendar preparation and invoices → SLACK runs 5 workflows for standups, thread summaries, support and mentions → GITHUB takes care of 5 engineering jobs, including PR reviews, issue labels, CI checks and dependency changes → EMAIL manages 4 jobs for invoices, lead drafts, receipts and newsletters → NIGHT RULE keeps 3 overnight workflows separate from actions that need human approval → MONDAY 09:00 runs 3 maintenance tasks: http://audit.py, Log Rotator and Cost Report the last one is my favorite. every monday, Cost Report tells you what each routine cost over the previous week. you can finally see which automations are useful and which ones are just burning money. here's how i'd organize the whole system: → events for things that need immediate attention → hourly checks for sources that change frequently → daily schedules for predictable reporting → night rules for work that shouldn't wake you up → weekly audits to catch waste and failures no need to turn every little task into another expensive AI session. the important part is assigning the right trigger before you enable anything. paste this into Grok Bot ↓ "Design a routine workspace with 8 trigger groups. 1. Organize my workflows across webhooks, hourly checks, daily schedules, Slack, GitHub, email, overnight rules and weekly maintenance. 2. Give every routine one specific responsibility and an expected output. 3. Use event triggers when supported instead of unnecessary scheduled polling. 4. Skip expensive processing when the underlying information hasn't changed. 5. Keep sensitive actions in draft mode until I approve them. 6. Create a Monday 09:00 Cost Report showing execution counts, failures, estimated spending and routines worth pausing. Show me the entire configuration before enabling anything." the dashboard uses 38 of Grok Bot's 50 available routine slots. but filling every slot isn't the goal. i'd rather have 12 jobs that finish real work than 50 agents competing to write the same useless status update. ↳ https://docs.x.ai/grok-bot/skills-routines-and-automations
这条是引用着另一条写的:x.com/gippp69/status/2109235458383216811