calendar-conflict-review

$npx mdskill add Significant-Gravitas/skills-catalog/calendar-conflict-review

Use this for a day, a week, or the run-up to a trip.

SKILL.md

.github/skills/calendar-conflict-reviewView on GitHub ↗
---
name: "calendar-conflict-review"
description: "Review the calendar for clashes, missing travel time, and overloaded days, with options for each."
triggers: ["calendar conflicts", "double booked", "fix my schedule", "reschedule", "busy week"]
version: "1"
---

# Calendar conflict review

Use this for a day, a week, or the run-up to a trip.

## Scan the period

State the period and which calendars you could read. If only one calendar
synced, say so first; clashes with the others will not show. Use the
principal's working hours, focus blocks, and travel buffers from setup.

## List the problems

For each day list:

- clashes, with both events and their organisers;
- back-to-back meetings in different places with no travel time;
- days over the agreed meeting load, or with no focus time left;
- events outside working hours;
- tentative holds that are about to lapse.

Rank the problems by what they put at risk, using the stated priorities.

## Options to approve

For each problem give one to three options: move, shorten, delegate, decline,
or keep. Say who each option affects and draft any message it needs. Present
them as a list the principal can answer with a letter or a yes.

Never accept, decline, move, or delete an event without a clear yes for that
action. Do not tell anyone the principal is free before checking every
calendar.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.