World Meeting Coordination Skill

Rank meeting windows across timezones in a clean, decision-ready format.

What this skill does

• - Converts candidate slots across multiple timezones (DST-safe via IANA/zoneinfo)
• Scores each slot for comfort
• Returns ranked sections:

• - Outputs Telegram-friendly formatting

Quick start

Natural-language prompt examples

• - "Find the best meeting windows for Chicago, London, and Tel Aviv on March 6, anchored to Chicago time. Return Optimal, Stretch, and Avoid windows with reasons."
• "Find overlap windows for San Francisco, New York, and Berlin on 2026-04-12 in Pacific time, 60-minute meetings."
• "Give me top 3 windows for Chicago, Paris, and Singapore tomorrow in Chicago time, with +1 day markers where needed."

CLI example

CODEBLOCK0

Inputs

Required:

• - --date (YYYY-MM-DD preferred)
• INLINECODE4 (name=IANA timezone pairs)

Optional:

• - --anchor (default: America/Chicago)
• INLINECODE7 meeting length in minutes (default: 60)
• INLINECODE9 slot step size in minutes (default: 60)
• INLINECODE11 top results per category (default: 3)
• INLINECODE13 your preferred hours, e.g. INLINECODE14
• INLINECODE15 per-participant hours map, e.g. INLINECODE16

Onboarding and settings

First interactive run auto-starts onboarding with 3 questions:

1. 1. Your timezone
2. Your preferred meeting hours
3. Your flexibility (strict, balanced, flexible)

Canonical chat phrase

• - INLINECODE20

Also treat these as setup intent

• - "set up meeting skill"
• "configure world meeting"
• "update my meeting hours"
• "set my scheduling preferences"
• "change my timezone for meeting windows"
• "show my meeting settings"

Settings commands

CODEBLOCK1

Settings file location:

• - INLINECODE21

Output format contract

• - Sections: Optimal, Stretch, INLINECODE24
• Numbered items (1., 2., ...)
• Anchor-time line first, then participant local lines
• Time format: INLINECODE27
• INLINECODE28 marker when local date rolls over
• Spacer line ⠀ between items for Telegram rendering
• Stretch/Avoid include italic reason line: INLINECODE30

Scoring model (default)

Per participant, local start time is scored:

• - In preferred window: INLINECODE31
• Near edge: low penalty
• Outside window: medium penalty
• Overnight/off-hours: high penalty

Total score maps to:

• - Optimal: low total
• INLINECODE33: medium total
• INLINECODE34: high total

Notes

• - Prefer IANA timezone names (example: Europe/London, not GMT+0).
• If user gives city names only, map city -> IANA timezone before running.
• If a category is empty, return the best available windows with a brief note.