Best Prompts for OpenWorker

"Show me my schedule for tomorrow. For each meeting, tell me who organized it, the agenda, and what I should prepare."

OpenWorker cross-references calendar events with email threads about those meetings to pull preparation context that the calendar entry alone does not contain.

"Find all meetings this week where I'm optional. Draft polite decline messages for any that conflict with my focus blocks."

Reclaims time by identifying optional meetings that overlap with deep work. OpenWorker reads attendee status and generates individual decline messages.

"Block two 90-minute focus windows this week on days that currently have fewer than 3 meetings. Name them 'Deep Work' and set them as busy."

Proactive calendar optimization. OpenWorker analyzes your week's meeting density and places focus blocks where they will survive best.

"Compare my calendar next week with [colleague name]'s calendar and find three 30-minute slots where we are both free."

Eliminates the back-and-forth of scheduling. OpenWorker reads both calendars (if the colleague has shared access) and suggests specific times.

"Generate a weekly project report covering: merged PRs from GitHub, completed issues from Linear, and key Slack discussions from #product."

The ultimate cross-integration OpenWorker prompt. It aggregates three data sources into a single report that would take 30+ minutes to compile manually.

"Create a summary of all customer feedback received this week from email and Slack. Categorize by theme: feature requests, bug reports, and praise."

Turns scattered feedback into actionable categories. OpenWorker reads both email and Slack conversations to find customer-related messages and classify them.

"Pull the key metrics from this month's sales dashboard spreadsheet on Google Drive and format them into an executive summary with bullet points."

OpenWorker accesses Google Drive, reads the spreadsheet data, identifies the most important trends, and formats them for executive consumption.

"Compare this week's GitHub activity (commits, PRs, reviews) with last week. Highlight any unusual changes in team velocity."

Trend analysis across two time periods. OpenWorker queries GitHub's API twice and performs the comparison automatically, flagging anomalies.

"Every morning at 8 AM, check my unread emails, today's calendar, and overnight Slack mentions. Compile a morning briefing and post it to #my-briefing."

The ultimate OpenWorker automation. Set this as a scheduled trigger and start every workday with a personalized briefing that covers all your communication channels.

"When someone mentions me in #support, check the customer's account in HubSpot, find relevant documentation in Notion, and draft a response for my review."

Multi-step trigger workflow. OpenWorker chains three integrations — Slack detection, HubSpot lookup, and Notion search — to produce a context-rich draft response.

"Review the attached document and create a Notion page with a structured summary. Then draft an email to the team with the key takeaways and a link to the Notion page."

Demonstrates OpenWorker's ability to chain outputs. The Notion page becomes an input for the email, creating a complete workflow from a single request.

"Every Friday at 4 PM, compile a weekly digest from GitHub PRs, Linear completed issues, and Slack highlights from #wins. Save it as a Google Doc and share the link in #team-updates."

Fully automated weekly reporting. Once configured as a trigger, this OpenWorker prompt runs every Friday without any manual intervention.