Research a decision
Compare three project-management tools for a five-person design studio. Use their current product and pricing pages, link your sources, and save a comparison with a recommendation and its tradeoffs.
Set up web search first. Tell the bot your budget and requirements, and ask it to separate facts from assumptions.
Turn a file into something useful
Use the attached support-ticket CSV to find our five most common issues. Include counts, show a few examples, and attach a summary plus a cleaned CSV. Keep the original file unchanged.
Attach the file in chat and say what format you want back. See files and results.
Prepare for a meeting
Review tomorrow's planning meeting and the project notes I linked. Prepare a brief with open decisions, overdue actions, and questions for each owner. Save it for me to review.
Connect your calendar and notes with plugins first. Name the calendar or project to use; don't expect the bot to find every source on its own.
Work on a codebase
Clone our website repository into /workspace/website. Find why the contact form loses its draft on navigation, fix it, and run the tests. Leave the changes for me to review.
The bot works in its own Linux environment, so tell it where to get the code and how to run the tests. To work on a folder on your own machine instead, use the local computer connection.
Send a recurring briefing
Every weekday at 9 AM, summarize the new issues assigned to me. Group them by project, include links, and call out anything due this week.
Run the task once in chat with your issue tracker connected. When the result looks right, save it as a routine.