Turn a working Grok Bot task into a reusable skill

Copy the template

Skill name: [Verb + business outcome]
Use when: [Trigger or request that should invoke this skill]
Required inputs: [Systems, fields, files and freshness requirements]
Steps: [Ordered actions with bounded reads and record limits]
Validation: [Checks, reconciliations, duplicates and evidence requirements]
Output: [Exact format, location, fields and source block]
Approval: [Actions the Bot must never take without a human]
Failure handling: [What to report and where to stop]

Keep the skill narrow

Name it Prepare overdue invoice review queue, not Manage finance. A narrow skill can be tested, corrected and reused by the appropriate Bot. A broad skill hides decisions inside an instruction nobody can audit.

Test before scheduling

• A normal case produces the required output.
• Missing input stops with a clear exception.
• Stale input stops before recommendations or drafts.
• A record above the approval threshold is separated for review.
• The evidence block identifies every source used.

When those tests pass, create the routine that invokes the skill on a schedule or supported event.