Grokbot TemplatesGrokbot Templates
Все сценарии

Работа

Routine reliability audit: six checks before you change anything

You notice a routine was idling or doing the wrong thing only after the week's usage is gone.

Поделиться

Что болело

@stansKoya tip (adapted from @Michael_Fenech_'s six-check idea): before you retune live schedules, run a ROUTINE RELIABILITY AUDIT. Each bot reports its routines; check unique owner, time/timezone/frequency, fresh inputs, what success looks like and where it lands, whether approval steps can go stale, and how missing info / disconnects / low quota are reported. Then pick the top three for a safe test plan — no live changes or dry-runs without approval (dry-runs still do real work and burn usage). Distinct from usage-auditor-holes-baseline (different six checks focused on routine reliability). Author-quoted Chinese prompt (EN translated). Not affiliated with xAI.

Что установить или создать

Paste audit prompt → each bot reports routines → six checks → top-three safe test plan → approve before any change or dry-run.

Боты

  • Новый бот не нужен. Следуйте шагам первого запуска.

Плагины

  • В первый день не нужны. Следуйте шагам первого запуска.

Рутины

  • На первом запуске их нет. Сначала пройдите один раз вручную.

Промпт

Routine reliability audit — six checks, change nothing without approval (author-quoted)

Quoted from @stansKoya (adapted from @Michael_Fenech_) — as published. Do not invent a second system prompt.

Последняя строка — наш барьер одобрения: Never send, post, spend, or buy without my explicit yes.

(Translated from the author's Chinese.)

Run a ROUTINE RELIABILITY AUDIT on my Grok Bot team. Have every Bot report its own routines. Check each one for: 1) whether there is a single owner; 2) whether time / timezone / frequency are sensible; 3) whether inputs use the latest sources; 4) what success looks like and where it is delivered; 5) whether steps that need my approval can go stale; 6) how missing info / disconnects / low usage quota are reported. Pick the three most important items and give me a safe test plan. Do not change or dry-run any live routine without approval — a dry-run still does real work and burns usage.

Never send, post, spend, or buy without my explicit yes.

Первый запуск

  1. 1Read https://x.com/stansKoya/status/2118145047325794655 (credit @stansKoya; six-check idea also @Michael_Fenech_).
  2. 2Paste the author ROUTINE RELIABILITY AUDIT prompt into your lead bot; require a report only.
  3. 3Review the six checks per routine: unique owner, schedule/timezone, fresh inputs, success shape + destination, stale approval steps, failure reporting.
  4. 4Approve a safe test plan for the top three findings only.
  5. 5Change or dry-run nothing live until you say yes — dry-runs still burn usage.

Барьер одобрения

Report only first — never change, pause, or dry-run a live routine without your yes.

Что поправить

Steal the six reliability checks; report first, don't burn usage on unapproved dry-runs.

Источник

Stans @stansKoya · Исходный пост

Не связаны с xAI. Этот промпт написали не мы. Условия сторонних шаблонов по-прежнему действуют.

Смотреть шаблоны

Смотреть схемы команд

Пакет Pro

Нужна полная настройка, а не только идея?

В пакетах Pro — текст задачи, промпты, расписания и подводные камни для популярных сценариев.

Смотреть Pro