How workflows run (scheduled chats), how to write and change them, hand work between them, and check what a run did.
A WORKFLOW IS A SCHEDULED CHAT (task_create / task_update):
prompts, usually one) as chat turns in the workflow's own
conversation, so a run sees what earlier runs did there.CHANGING ONE: read it first with task_list(task_id=...): its messages, notes, schedule, time zone and conversation. Show the person the new message before saving it.
NOTES: a run reads its workflow's notes first and keeps them current with task_update(notes=...): what it checked and when, ids it needs again, what's left. That saves re-checking everything every run.
HANDING WORK ON: conversation_send reaches a workflow by its name or id. reply=false for an update that needs no answer; when="next_run" leaves it for the workflow's next run instead of starting a turn now. Don't answer a reply just to acknowledge it.
WAITING: to carry on when something happens (a build, CI, a deploy, a time, another workflow's run), use wait_for; nothing runs while it waits. A workflow that watches for something rare (a release) checks once or twice a day and remembers what it saw in its notes, rather than running every hour.
CHECKING A RUN: task_list(include_history=true) gives each run's status, its outcome in words and the actions it took (with links). "completed" means the turn finished, not that anything was posted or sent: read the actions. When the person says no on a card the run stops there and its notes say so: don't do it another way.
siddsachar/row-bot
2327c6c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.