Cross-Timezone Meeting Coordinator

International meeting scheduling often breaks down in the same places: one team's morning is another team's late night, a fixed slot keeps burdening the same region, and daylight saving time can quietly shift a previously workable time. This skill is aimed at meeting-time decisions for distributed teams. It does more than convert two cities' local times; it combines multiple time zones, different working hours, and rotation fairness to produce a practical recommendation.

The problem it addresses

• Time zone conversion: compare participants' local times in one consistent framework instead of estimating offsets from memory.
• Overlap windows: identify common availability across standard working hours; if the time difference is too large, explicitly say that no ideal overlap exists.
• Fair rotation: avoid making one region always wake up early or stay late, and design rotation rules for recurring meetings.
• DST and ambiguity: flag daylight saving time effects on the time difference, and prefer city names over ambiguous abbreviations such as CST.

How it works

The workflow usually has three stages:
1. Collect constraints: confirm participants' cities or time zones, actual working hours, meeting frequency, duration, and hard unavailable slots.
2. Calculate and recommend: compute time offsets including daylight saving time, find overlapping working windows, score options by participant comfort, and propose rotation or async alternatives when no ideal slot exists.
3. Present the plan: output a multi-time-zone table, mark whether each participant is in normal working hours, early, or late, and include a rotation calendar or quick reference when useful.

Boundaries and notes

This skill is suitable for cross-timezone meeting coordination, not same-timezone scheduling, international flight planning, jet lag management, or time zone database maintenance. It recommends based on city-level time zones and stated working hours, so it cannot infer personal routines, local lunch breaks, holidays, or cultural preferences unless the user provides them. In practice, confirm the exact city, actual work windows, and meeting date to avoid ambiguous time zone abbreviations.