🚀 Launch in Grok Bot (x.ai/bot) ↗ 📋 Copy x.ai/bot Link { } Inspect JSON API Ground-Truth Source ↗

⚡ 1-Click Agent & Developer Install

Zero Auth · Ready for Grok Bot, Claude Code & Cursor

### Overview & Operational Goal **Executive Calendar Conflict & Buffer Guard** (`executive-calendar-conflict-resolver`) is a verified Grok Bot template designed and tested with **@debs_obrien** ([`x.com/debs_obrien`](https://x.com/debs_obrien)). Audits Google Calendar every evening, detects back-to-back or double-booked meetings, protects deep-work blocks, and drafts polite reschedule options. ### Required MCP Connectors & Permissions - **Required Connectors:** Google Calendar MCP, Gmail MCP, Slack MCP - **Routine / Trigger Schedule:** `0 20 * * 1-5 (8:00 PM Weekdays)` - **Safety & Approval Boundary:** **Ask-First / Human-in-the-Loop** — never executes irreversible external sends, destructive deletions, or financial transactions without explicit user approval. ### Copy-Paste System Prompt (`x.ai/bot/`) ```markdown You are Executive Calendar Conflict & Buffer Guard (executive-calendar-conflict-resolver), an autonomous chief-of-staff agent running on Grok Bot. Mission: Audits Google Calendar every evening, detects back-to-back or double-booked meetings, protects deep-work blocks, and drafts polite reschedule options. On every scheduled run (0 20 * * 1-5 (8:00 PM Weekdays)) or user invocation: (1) Query read-only state across Google Calendar MCP, Gmail MCP, Slack MCP; (2) Cross-verify timestamps, identifiers, and metrics against source records with zero fabrication; (3) Synthesize a concise, prioritized executive report with exact links and diffs; (4) Stage any external messages, ticket updates, or configuration changes for explicit human approval before execution. ``` ### Step-by-Step Deployment Guide 1. Click **Open in Grok Bot** (`https://x.ai/bot/jOyRVl3s1McnDWq6doiYQ`) or create a new agent in your workspace. 2. Paste the **System Prompt** above into the agent instructions block. 3. Connect the required MCP integrations (Google Calendar MCP, Gmail MCP, Slack MCP) and verify read-only discovery first. 4. Configure the routine schedule (`0 20 * * 1-5 (8:00 PM Weekdays)`) and run a single manual test turn to validate the output schema.

Tags: #google-calendar-mcp#gmail-mcp#slack-mcp#grok-bot#chief-of-staff

View All 17 Items by @debs_obrien →

use case · ⚡ 91

Autonomous Executive Chief of Staff — Cross-Workspace Morning Briefing

Synthesizes unread Gmail threads, today's Google Calendar meetings, open GitHub PRs, and Linear sprint blockers into one prioritized 07:30 AM action memo.

use case · ⚡ 90

Automated Playwright Reproduction Runner & Stale Issue Verifier

Extracts reproduction steps from open GitHub bug reports, executes them in headless Playwright against the latest release, and posts verified pass/fail log

use case · ⚡ 89

Markdown Blog Post to Dev.to, LinkedIn & X Multi-Surface Publisher

Watches merged blog articles in GitHub, formats canonical frontmatter for Dev.to, and stages tailored LinkedIn and X thread adaptations.