Skip to content

Calendar guard

Protects focus time and catches double bookings.

PersonalWorks with ChatGPT agent · Claude Desktop with MCP+2

What it does

  • Spots conflicts
  • Suggests new times
  • Holds focus blocks

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Accepting or declining invites

You decide what happens next.

More about this workflow

This setup is for busy people who want their own day to run a little smoother. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it spots conflicts. Next, it suggests new times. Finally, it holds focus blocks. It works with your calendar, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before accepting or declining invites, and says plainly if a step cannot be undone.

Before you startCalendar accessScoped permissionsChatGPT agent or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Google Calendar

    Handles the calendar part of this job. Grant read-only calendar scope.

    API required: Yes. Needs a Google Cloud OAuth app with the Calendar API turned on.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Fast and careful with your inbox and calendar.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Haiku 5.5

Cheapest Claude option for daily sorting.

From $0.10 per million input tokens and from $0.50 per million output tokens.

Anthropic docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

days and times

2Your prompt

3 of 3 still empty
Fill these in before you run it: [YOUR CALENDAR] [YOUR WORKING HOURS AND TIME ZONE] [YOUR FOCUS BLOCKS: days and times] You are the Calendar guard agent. Protects focus time and catches double bookings. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Spots conflicts - Suggests new times - Holds focus blocks What you must never do without a yes from a person: - Accepting or declining invites Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: ChatGPT agent, Claude Desktop with MCP, Custom GPTs, Zapier Agents

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Google Calendar with its own login, not yours. Grant read-only calendar scope.
  2. 2Paste the prompt where your harness takes instructions. See the note under the Copy button.
  3. 3Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  4. 4Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval27 / 30

Waits for a yes on: accepting or declining invites.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope20 / 20

Runs on its own login across 1 tool. Fewer connections means a smaller blast radius.

How to raise it

  • Human approval: Add a second named stop next to "accepting or declining invites", so every step that leaves your hands waits for a yes, and have the confirm say plainly what cannot be undone +3
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3

Do all of these to reach 91, up from 85.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Calendar guard](https://trustcase.dev/badge/calendar-guard.svg)](https://trustcase.dev/use-cases/calendar-guard)
HTML
<a href="https://trustcase.dev/use-cases/calendar-guard"><img src="https://trustcase.dev/badge/calendar-guard.svg" alt="Trustcase trust score for Calendar guard" height="20"></a>