Common uses
Example tasks you can send as written: summarizing, acting across tools, meetings and calls, files and numbers, and scheduled routines.
How to use this page#
Every example below is something you can send to Stevin as it is. Replace the channel, repository and table names with your own. The tools involved need to be connected first under Integrations or MCP servers.
Summarizing information#
- "Summarize today's discussion in this channel into conclusions and action items, and put an owner on each action item."
- "Summarize the pull requests merged last week, grouped by module, and write a short update for non-technical colleagues."
- "Compare these two documents and list where they conflict."
Acting across tools#
- "Create a Linear issue from this piece of user feedback, set the priority to high, and post the link back in this thread."
- "Add this week's completed items to the weekly report page in Notion."
- "Look up this customer's recent contact history in HubSpot and draft a follow-up email. Show it to me first."
These tasks include write actions, so Stevin asks for your approval first.
Meetings and calls#
- "Turn this recording into notes and extract decisions and action items." Send the recording in chat; the transcript and summary land in the library.
- Talk in Live and let it work while you speak. Afterwards the transcript and summary are in the library.
- From the car: call Stevin, ask for what you need, and say "run it in the background and send me the result".
Files and numbers#
- "Total the hours per project in this sheet and give me a spreadsheet."
- "Draw a weekly trend chart from these figures."
- "Check the arithmetic in this quote."
Stevin does these with code execution, and the files it produces are kept in the library.
Scheduled routines#
These work well as automations:
- At 9:00 every weekday, post a summary of yesterday's GitHub activity to a channel.
- When a new lead is added to a table, assign it to the right salesperson by region and remind them.
- Every Friday, group the week's customer feedback by product area and write a weekly report.
You can also just say it in chat: "From now on, do this at 9:00 every weekday morning." Stevin sets up the automation for you.
Three habits for writing good tasks#
- Hand over one thing at a time. Split large tasks.
- Give the criteria for judgment calls, for example "high priority = affects paying customers".
- For work that recurs, write a skill so you do not have to explain it every time.