Time Zone Planner
by @aipoch-ai
Plan cross-time-zone meeting windows for distributed teams, providing region-by-region local time mappings and tradeoff analysis for scheduling decisions.
clawhub install time-zone-plannerπ About This Skill
name: time-zone-planner description: Plan cross-time-zone meeting windows for distributed teams, providing region-by-region local time mappings and tradeoff analysis for scheduling decisions. license: MIT skill-author: AIPOCH
Time Zone Planner
Structured cross-time-zone meeting planning for distributed teams.
Quick Check
python -m py_compile scripts/main.py
python scripts/main.py
When to Use
Workflow
1. Confirm the participant regions, meeting duration, preferred local-hour ranges, and any hard constraints. 2. Check whether the request is for a quick overlap recommendation or a full tradeoff analysis. 3. Use the packaged script for baseline scheduling output; for complex requests, provide a manual comparison table with stated assumptions. 4. Return suggested meeting windows, region-by-region local times, and the tradeoffs behind the recommendation. 5. If timezone details or availability constraints are missing, stop and request the minimum missing fields.
Usage
python scripts/main.py
Input: {"regions": ["US", "EU", "Asia"], "duration": 60}
Parameters
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| regions | list[string] | Yes | β | Region set, e.g. ["US/Eastern", "Europe/London", "Asia/Shanghai"] |
| duration | integer | Yes | β | Meeting duration in minutes |
| preferred_hours | object | No | β | Per-region preferred local hour ranges, e.g. {"US/Eastern": [9, 17]} |
Region format: Use IANA timezone names (e.g., US/Eastern, Europe/London, Asia/Shanghai) for precise mapping. Short aliases like "US" or "EU" are accepted but will be mapped to a representative timezone with a note.
Region Alias Mapping
| Alias | Mapped To | Note |
|-------|-----------|------|
| US | US/Eastern | Representative only; specify sub-region for accuracy |
| EU | Europe/London | Representative only; specify country for accuracy |
| Asia | Asia/Shanghai | Representative only; specify city for accuracy |
Output
Scope Boundaries
Stress-Case Rules
For multi-constraint requests, always include these explicit blocks:
1. Assumptions 2. Hard Constraints 3. Recommended Window 4. Tradeoffs 5. Risks and Manual Checks
Error Handling
scripts/main.py fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.Input Validation
This skill accepts: a list of participant regions and a meeting duration for cross-timezone scheduling recommendations.
If the request does not involve cross-timezone meeting planning β for example, asking to book calendar events, check live availability, make travel arrangements, or provide legal scheduling advice β do not proceed with the workflow. Instead respond: > "time-zone-planner is designed to recommend meeting windows across time zones for distributed teams. Your request appears to be outside this scope. Please provide a region list and meeting duration, or use a more appropriate tool."
References
Response Template
Use the following fixed structure for non-trivial requests:
1. Objective 2. Inputs Received 3. Assumptions 4. Workflow 5. Deliverable 6. Risks and Limits 7. Next Checks
If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.
β‘ When to Use
π‘ Examples
python scripts/main.py
Input: {"regions": ["US", "EU", "Asia"], "duration": 60}