Audit calendar conflicts and buffers

TASK SETTINGS — fill only what is relevant
Scope: [selected accounts, records, or task]
Budget: [amount and currency, or no new spending]
Deadline: [date, time, and timezone]
Tone: [polite and concise]
Contact channel: [no contact until approved]
Approval: Read-only first. Ask before sending, calling, submitting, cancelling, booking, paying, signing, or changing anything.

Find scheduling problems before they become missed commitments.

Use only the accounts and materials I authorize. Start with: the calendars I authorize, next two weeks, working hours and realistic travel preferences.

Identify overlapping events, duplicate invites, timezone inconsistencies, missing travel buffers and recurring meetings that collide with leave. Distinguish declined, tentative and accepted entries. Check location changes against reasonable travel assumptions. Propose the smallest changes that resolve each conflict while preserving my priorities.

Work read-only and prepare drafts first. Before contacting anyone, sharing information, changing an account, booking, spending, submitting a form or modifying files, show me the exact action and obtain my approval. Do not delete, decline, reschedule or notify attendees automatically.

Verify that your tools actually support the requested work. After two different failed access attempts, report the blocker and finish the accessible parts instead of looping. Never invent an action, source, availability or confirmation.

Return: a conflict table with original event links, severity, minimal proposed correction and approval needed. Separate verified facts, assumptions, proposals, and completed actions. This first pass is finished when the requested evidence and next decision are delivered, not when an unapproved action is taken.

For ongoing checks, propose a cadence, timezone, trigger, end date and any cost. Do not claim monitoring is active until I approve and you return the actual task ID and next run. Respect service rules and rate limits; do not bypass anti-bot controls. Keep a manual backup for critical deadlines.

Standing-brief setup: First perform one read-only baseline check. Then propose the exact schedule, timezone, end/review date, trigger, cost limit, and notification destination for my approval. Create a recurring task only after approval and only with a real scheduler. Return the actual task ID, next run, and pause/stop instructions; otherwise say it is not scheduled. On subsequent runs, compare with the last successful checkpoint, deduplicate alerts, retain only necessary state, and report failures or stale access rather than treating them as no change. Respect service rules and rate limits. No external actions are authorized by a scheduled check.