Trabajo
Teach skills as SOPs before you spawn more bots
More bots still rediscover the same workflow every morning.
Qué dolía
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.
Qué instalar o crear
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.
Bots
Approver
Exists before workers. Can say no on send, spend, delete, publish.
Worker
Runs a named Skill the same way every time.
Plugins
Ninguno el primer día. Sigue los pasos del primer uso.
Rutinas
Only after one Skill works by hand: schedule or event trigger for that Skill. Approver still gates side effects.
El prompt
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.
La última línea es nuestra valla de aprobación: 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.
Primer uso
- 1Pick one repeatable job you already trust by hand.
- 2Create a Skill with process, inputs, rules, validation, output format, and approval boundaries.
- 3Attach the Skill to one existing bot; run it once and fix the Skill, not the chat history.
- 4Add or keep an approver that can refuse send, spend, delete, and publish.
- 5Only then attach a Routine.
Valla de aprobación
Skills and routines stop before send, spend, delete, or publish until a human says yes.
Qué ajustar
Bots are employees. Skills are SOPs. Routines are cadence. Approver first. Steal the structure, not his TORQ stack.
Fuente
DigitalAssetBuzz @DAssetBuzz · Publicación original
Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.
Paquete Pro
¿Quieres la configuración completa, no solo la idea?
Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.