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

Работа

Teach skills as SOPs before you spawn more bots

More bots still rediscover the same workflow every morning.

Поделиться

Что болело

DigitalAssetBuzz watched people spin up more Grok Bots while the real leverage sat unused: Skills. A Skill can hold process, inputs, decision rules, validation, output format, and approval boundaries so any suitable bot reuses a tested playbook instead of improvising. Separately, he built the approver bot before the worker — someone who can say no — because that gate is the part nobody automates.

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

Write one Skill for a job you already do by hand: process, inputs, rules, validation, output shape, and what needs a human yes. Attach it to an existing bot (researcher, post creator, growth) so it runs that process, not a vague chat. When the Skill is stable, hang it on a Routine for a schedule or event. Build or keep an approver that workers report to before send, spend, delete, or publish.

Боты

  • Approver

    Exists before workers. Can say no on send, spend, delete, publish.

  • Worker

    Runs a named Skill the same way every time.

Плагины

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

Рутины

  • Only after one Skill works by hand: schedule or event trigger for that Skill. Approver still gates side effects.

Промпт

Skill skeleton to paste when creating a Skill

Curated from DigitalAssetBuzz’s published Skill definition in the cited post. Not a full Skill body he pasted.

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

Capture this job as a Skill:
- process steps
- required inputs
- decision rules
- validation checks
- exact output format
- approval boundaries (stop before send, spend, delete, or publish)

Any appropriate Bot should be able to reuse this instead of rediscovering the workflow. Do not improvise past the Skill.

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

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

  1. 1Pick one repeatable job you already trust by hand.
  2. 2Create a Skill with process, inputs, rules, validation, output format, and approval boundaries.
  3. 3Attach the Skill to one existing bot; run it once and fix the Skill, not the chat history.
  4. 4Add or keep an approver that can refuse send, spend, delete, and publish.
  5. 5Only then attach a Routine.

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

Skills and routines stop before send, spend, delete, or publish until a human says yes.

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

Bots are employees. Skills are SOPs. Routines are cadence. Approver first. Steal the structure, not his TORQ stack.

Источник

DigitalAssetBuzz @DAssetBuzz · Исходный пост

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

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

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

Пакет Pro

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

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

Смотреть Pro