Individual skill
scheduling
Find meeting or appointment times, create private calendar holds or invitations, and reschedule or cancel events within the user's authorization. Not for automations.
OpenAI/dots/skills/scheduling/SKILL.md
Source commit a2d33761e49b98f6ec1b48f12143264eb9b4ff4f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 71,199
- Repository last updated
- Nov 10, 2026
- License
- CC0-1.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- anthropic Repository topic
- chatbot Repository topic
- chatgpt Repository topic
- claude Repository topic
- claude-code Repository topic
- codex Repository topic
- gemini Repository topic
- generative-ai Repository topic
- google Repository topic
- productivity Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,554 bytes
Read excerpt
# Scheduling
Find an arrangement that works in practice, and distinguish suggested times, private holds, invitations and confirmed appointments.
## Find a time
- Establish the people, purpose, date range, duration and location from the request and latest conversation. Check whether a venue, organizer or required attendee controls the time. Resolve relative dates in the user's time zone; name the exact date and local time when time zones or daylight saving could cause confusion.
- Check current availability and known working hours, travel, focus blocks and buffers. Use relevant preferences, but follow the current request first. Account for travel time and whether a recently changed itinerary makes the usual time zone or location unreliable.
- If there are no slots available for all participants in the timeframe requested, understand the options with the fewest or least problematic conflicts. A conflict is likely to be less problematic if it is optional or can be easily rescheduled for all required attendees. Use what you know about the user, their priorities, and the priorities of their team when reasoning about which conflicts are better to surface as options.
- Pick the strongest options and explain only the useful tradeoff. If none works, suggest another day, a remote meeting or moving a flexible event. Ask only if the move falls outside the permission given or a consequential detail is unclear, such as which of two same-named people to invite.
- If you cannot see someone else's calendar, call the times proposed, not confirmed. Do not reveal private calendar details. Distinguish tentative holds from confirmed conflicts; do not overwrite or move either without authority.
## Make and check the change