
Scheduling Coordination
Coordinates availability and calendar changes, verifying each one by read-back.
Install
npx skills add odysseus-dev/odysseus --skill scheduling-coordination -g -a claude-code -y- Repository
- odysseus-dev/odysseus94.9k
- Category
- Business
- Updated
- 3d ago
- License
- AGPL-3.0
- Context cost
- Lightabout 374 tokens
- Runs scripts
- No, instructions only
What it does
Coordinate availability, confirmations, calendar changes, and participant notifications with read-back verification
When to Use
Use when arranging or changing a meeting across multiple participants, calendars, time zones, or communication channels.
Do not create or modify an event when the user asked only for available options or a draft invitation.
Procedure
- Extract participants, duration, date range, time zones, location constraints, and required attendees.
- Resolve participant identities and inspect the relevant availability using declared calendar and contact capabilities.
- Compute candidate intervals in one explicit reference time zone and reject conflicts or insufficient travel buffers.
- Present or draft a small set of viable options when confirmation is still required.
- After authorization or recorded participant confirmation, create or update the event once with stable attendee identifiers.
- Read the event back and verify title, start, end, time zone, attendees, location, and conferencing details before drafting notifications.
Pitfalls
- Do not overwrite or cancel unrelated events to manufacture availability.
- Do not mix local times without naming the time zone.
- Do not treat a proposed time as confirmed.
- Do not create duplicates when an existing event can be updated safely.
Verification
- The selected interval satisfies duration, availability, and time-zone constraints.
- The calendar read-back matches the authorized event details.
- Notifications describe the same confirmed event and remain drafts unless sending was explicitly authorized.

