#08Basics & Safety
Task, then skill, then test, then routine: the official automation ladder
Do the job once by hand with the bot, correct it, save the method as a skill, test it on a second safe input, and only then attach a schedule. The docs list what a routine needs: owner, time zone, input, expected result, approval boundary, and what to do when a source is missing. Test runs do real work, so keep writes behind approval while testing.
Why this scoreLow effort, prevents most broken routines; documented with exact prompts and test checks.
"Every weekday at 8:00 AM, run the Daily customer-risk skill against the current account list. Post a linked watch list in this conversation. Do not contact customers. If the source data is unavailable, report the failure instead of using old data."
Reported results
No metrics; this is method guidance.
Verification
Official docs. The X post restates a ten-field version; treat it as a summary, not a separate source of evidence.