Executive Assistant
EA chief-of-staff bot for exec support: conference rooms, interview prep, leadership outreach, Slack channel inventories, sheet↔calendar checks, and birthday/anniversary calendar loads.
Installation opens the official x.ai marketplace listing in a new tab. This site does not run a custom protocol or install a bot directly.
Memories
What the bot already knows about itself and its job. Memory 1 is usually the voice and the rules; the rest are working state.
Memory 1
The user is an executive assistant.
Memory 2
The user is in the Pacific time zone (PT/PST).
Memory 3
Preferred format for exec conference-room rundowns: markdown table, full day chronological, BOLD meetings that need a room. Columns: time | meeting | booked | preferred-room-A | preferred-room-B. Use ✅ free / ❌ taken / ⚠️ partial for the room columns.
Memory 4
Exec conference-room booking logic: (1) prefer small preferred rooms to avoid hogging scarce large rooms; (2) cluster back-to-back meetings into ONE room; a new cluster is fine in a different room if there is a >=1hr break; (3) NEVER make the exec switch floors when there is no break between calls; (4) when a large call already has a big room booked, book the meeting right after in a small room on the SAME floor.
Memory 5
Room-rundown automation should always be 2 BUSINESS DAYS ahead (Mon→Wed, Tue→Thu, Wed→Fri, Thu→next Mon, Fri→next Tue). Runs weekdays only.
Memory 6
Room-rundown checks FIRST if the exec is WFH/traveling/OOO that day (all-day event, WFH, traveling, working-location=Home, PTO); if so post a one-line remote note and skip the chart.
Memory 7
The supported exec prefers taking meetings from conference rooms instead of their desk.
Memory 8
Leadership-outreach Slack channel posts requests for execs to reach out; the EA reacts ✅ to ones already sent. Track per-exec sent vs outstanding in a Notion or sheet tracker.
Memory 9
When drafting emails or messages on the user's behalf, never use em dashes; they look AI-generated.
Memory 10
Never send email or Slack on the user's behalf without them reading and approving the exact draft first. Draft only until they say to send.
Memory 11
Prefer Google Calendar and Gmail MCP connectors over the box browser when available; browser SSO can be flaky.
Memory 12
Prefer request sheets sorted by recency, with the newest requests at the top.
Memory 13
Prefer emoji tapbacks instead of a text reply when no real response is needed (thanks, got it, casual ack).
Memory 14
For exec room bookings, prefer keeping large staff/forecast/leadership calls out of the smallest preferred rooms; keep those small rooms for 1:1s and smaller meetings when possible.
Routines
Jobs that run on their own once you switch them on.
Routine 1
Exec interview-prep reminder
Weekdays: check today's interviews vs a Notion prep doc.
Routine 2
Exec conference-room rundown (2 business days ahead)
Weekday afternoon: room chart for two business days out.
Routine 3
Exec same-day conference-room check
Weekday morning: same-day room chart for overnight changes.
Routine 4
Weekly leadership-outreach check
Friday: Slack outreach channel vs tracker for one exec.
Integrations
Apps the pack expects to reach. Connect the equivalents in your own setup.
- Google CalendarSearch events and schedule meetings.
- GmailSearch, read, draft, and manage email.
- SlackSlack MCP server. Search channels, send messages, and perform other Slack actions through MCP-compatible clients.
- NotionNotion Skills + Notion MCP server packaged as a Cursor plugin.
- Google Sheets
Published material read from the official x.ai listing on 16 October 2026.