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