← Zovo Meeting PlannerCONTENT HISTORY
WHAT CHANGED
Update to Zovo Meeting Planner
Snapshot Oct 28, 2026 · 13:07 UTC · version 1.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Zovo Meeting Planner and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Convert times between cities and time zones with exact daylight saving time handling (convert_time), and find meeting times for 2-8 places with working hours and .ics calendar files (find_meeting_time).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 484
}
],
"name": "meeting-planner",
"skill_md_contents": "---\nname: meeting-planner\ndescription: Convert times between cities and time zones with exact daylight saving time handling (convert_time), and find meeting times for 2-8 places with working hours and .ics calendar files (find_meeting_time).\n---\n\n# Zovo Meeting Planner\n\nUse `convert_time` for \"what time is X in Y\" questions (time zone converter, PST to EST, EST to IST, New York to London).\nUse `find_meeting_time` to plan a meeting across time zones or to see a team's working-hour overlap.\n\n1. Always pass explicit dates as YYYY-MM-DD (resolve \"next Tuesday\" yourself). Offsets depend on the date.\n2. Places can be cities (\"Bangalore\", \"Portland, Maine\"), IANA zones (\"Europe/Berlin\"), US states, countries, UTC offsets (\"UTC+5:30\"), or abbreviations (\"PST\", \"CET\"). Prefer the city the user named over an abbreviation.\n3. For `find_meeting_time`, list the organizer first (their dates define the range), keep ranges to 14 days or less, and pass `work_start`/`work_end` or per-person `work_days` when the user mentions them.\n4. Report the result's `status_note`, `difference_note`, `dst_note`, and `notes` to the user: they explain skipped or repeated times, clock changes within 7 days, and ambiguous abbreviations (IST, CST, AST, BST).\n5. For meetings, lead with slot 1 and each person's local time. Mention `start_window` (every start in it works for everyone) and `also_on` (other dates with the same local times). If `has_full_overlap` is false and `next_full_overlap` is present, tell the user that closest time that works for everyone, just after their dates.\n6. Share the `.ics` link for the slot the user picks. To get a calendar file for a different start, call `find_meeting_time` again with `selected_start_utc`.\n\nDo not use these tools for questions about the history or politics of time zones, writing emails, booking travel, or unit conversion. They do not read calendars, check availability, send invitations, or account for public holidays.\n"
}SHA-256 of public snapshot: a1bbd5500d4a2a0975ba01fe578a4320191e25ce86af05c46079f1a24eb73c6a