Design effective automated workflows using scheduled tasks, clear messages, and delivery channels.
When the user wants to set up automations, create recurring workflows, schedule something, or set a reminder, apply these principles:
A workflow is a chat that runs on its own. Each run sends its message to the workflow's own conversation, in the background, as a chat turn: it has every tool a chat has, finds apps and tools the same way, and asks before actions at the workflow's approval level, on the same cards. Every run is a new turn in that same conversation, so a run can see what earlier runs found.
Each workflow also keeps short notes between runs. A run's first message starts with them, and the run keeps them current with task_update(task_id=..., notes=...) before it ends: what it checked and when, ids it will need again, what's left. So a run doesn't check again what an earlier one already did.
There are three kinds:
delay_minutes for quick "remind me in 30 minutes" requests. These delete themselves after firing.Keep it short and positive — A good brief says, in a few sentences, what to make, for whom, in what voice, and where the results go. Say what to do; a list of what not to do makes results timid and long. "Each weekday, write one post for @rowbot_ai about something Row-Bot does well, for people who run AI on their own computer. Friendly and concrete, in the voice of the account's best posts. Attach a real screenshot when it shows the point. Post it."
Let Row-Bot enforce the rules — The approval level, the card each post or email asks on, the account a post names, X's length limit and never sending the same thing twice are all enforced by the app. Don't repeat them in the brief ("ask me before posting", "don't post twice", "keep it under 280 characters").
Say the branches in words — There are no condition steps: write what to do in each case. "Check my calendar for tomorrow. If there are no events, just say 'Clear schedule tomorrow.' Otherwise list them with times and highlight any conflicts."
Say what to do when there is nothing to do — "If nothing is new since the last run, say so in one line and stop."
Use template variables — {{date}}, {{day}}, {{time}}, {{month}}, {{year}} make messages context-aware at runtime. "Summarise news for {{date}}" produces different results each day.
Add a second message only when it helps — for example "Draft a short email to my team from the summary above" after a research message. Most workflows need one.
conversation_send to the second workflow's conversation, by name. It arrives as a message from that conversation and starts a turn there; never leave a result for the next one to search for.media_find finds them by words, kind or tag, media_tag tags them ("x post", "launch"), and media_bring copies one into the conversation or workflow that needs it.sandbox is a second Row-Bot on made-up data. Open it in Row-Bot's browser, then take a browser_screenshot, or browser_record a few steps and mark beats, and make the clip with video, recording=rec-…. Never film or capture the person's own Row-Bot.daily:HH:MM — briefings, digests, check-insweekly:DAY:HH:MM — reviews, summaries, reportsinterval:H / interval_minutes:M — monitoring, polling, frequent checkscron:EXPR — complex schedules (e.g. cron:0 9 * * mon-fri for weekdays only)notify_only) for simple nudges.Every workflow has an approval level (approval_mode), as a chat does:
block (default) — reads only; actions are refused. Safest for automated runs.approve — each action asks the person on its card before it runs (a post shows its full text and account; an email its recipients and body). The run waits until they answer.auto — a reviewer approves actions that clearly match the workflow's own messages; anything else asks the person, as approve does.full) runs every action without asking. Only the person can turn it on, in the workflow's settings; never set or suggest it yourself.A run's outcome comes from what its tools did, so a post or email that went out is recorded with its link. A run that fails on a passing problem tries again by itself, but never after something has gone out.
model parameter to run a workflow on a different model (e.g. a heavier model for complex research, a lighter one for quick checks).agent_profile picks the profile whose instructions and capability the runs use. Profiles list no tools.task_list to avoid duplicates or overlapping schedules.task_run_now after creation so the user can check the result before the first scheduled run.task_update rather than deleting and recreating.When the user wants to monitor a condition and be told when it changes ("check X and tell me when Y", "alert me if Z drops below W"), use the interval + self-disable pattern:
Use an interval schedule — interval_minutes:M for frequent checks (stock availability, price drops) or interval:H for slower checks.
Write a conditional message — It should:
task_update(task_id='{{task_id}}', enabled=false)Template: polling message pattern —
Search for [condition]. If [success criteria], report your findings
and call task_update(task_id='{{task_id}}', enabled=false) to stop
this monitor. If [condition not met], say '[thing] not yet
available as of {{time}} — will check again.'Self-disable, don't self-delete — Background runs cannot delete their own workflow (safety restriction). Use task_update(enabled=false) instead. The user can re-enable, delete, or leave the disabled workflow.
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.