About this skill

Problem

Cross-timezone work makes it easy to misread HH:MM, AM/PM, and date-specific conversions when moving between cities. Manual lookup becomes less practical when meetings, logs, shifts, or deadlines span UTC, America/New_York, Asia/Shanghai, and Asia/Tokyo.

How It Works

Input the source and target zones with --from and --to, plus --time; --date accepts YYYY-MM-DD and defaults to today when omitted.
Supported time formats include HH:MM, HH:MM:SS, and HH:MM AM/PM, covering 24-hour and 12-hour input.
Zone names follow the IANA timezone database, such as America/Chicago, Europe/Paris, and Australia/Sydney.
Conversion is based on Python's zoneinfo module for Python 3.9+, with automatic daylight-saving time handling and timezone offsets shown in the output.

Limits

Best for one-off time checks, meeting-time conversion, log timestamp alignment, and cross-timezone deadline checks; not a replacement for calendar systems, bulk historical conversion, or custom-offset and legacy zone-name workflows.

Screenshots

Use Cases

Schedule a cross-timezone review by converting Shanghai 3:00 PM to London and Tokyo times.
Audit an incident log by converting UTC 14:30 to US Eastern time and confirming the start point.
Write a duty handover note by converting US Pacific 09:00 AM to Singapore time.
Prepare an international meeting invite by converting a UTC date and 16:00 to Sydney and Paris.

Best For

Project managers coordinating cross-border meetings who need one timestamp converted into IANA zones with DST checks.
Backend engineers building scheduling or on-call systems who need UTC times converted to US or Asia site times.
SREs handling ops logs who need to cross-check UTC or city-local timestamps against another zone.
Developers writing international product docs who need user-local timezone equivalents in copy.