sync-calendar
Skill1 starsChanged 4 months agoMITView on GitHub
This skill should be used whenever the user wants the trip in their calendar — phrases like "add it to my calendar", "put the flights in Google Calendar", "calendar the itinerary", "block out the trip", "remind me about check-in", or proactively (as an offer, once) when an itinerary reaches Settled status.
In this repository15 other files it gives its agents.
- expense-reportSkill
- export-itinerarySkill
- find-activitiesSkill
- find-diningSkill
- find-flightsSkill
- find-staysSkill
- fun-factsSkill
- manage-itinerarySkill
- monitor-faresSkill
- on-trip-conciergeSkill
- plan-tripSkill
- traveller-profileSkill
- trip-budgetSkill
- trip-checklistsSkill
- trip-weatherSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Always propose adding an all-day "Trip: <title>" event spanning the whole trip, and useful reminders (online check-in opens, …
- Very specific: line 35
Read itinerary.md as the source of truth.
- Distinctive: line 37
Time zones matter most here: create events in the destination's local time zone.
- Distinctive: line 42
Put booking references, addresses and links in the event description, and the venue address in the location field so maps work from the …
- Distinctive: line 48
When the itinerary changes after a sync, offer to update the calendar too: find the existing events for the changed items and update rather …
- Distinctive: line 55
Create nothing without the traveller's go-ahead on the level of detail.
- Distinctive: line 56
Never store payment details in event descriptions.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sync Calendar
Push the trip into Google Calendar so the itinerary lives where the traveller already looks.
What to create
Offer two levels and let the traveller choose:
- Just the essentials — flights (with flight numbers and terminals in the title), stay check-in/check-out, and any timed, booked activities or reservations.
- The full itinerary — the essentials plus one all-day event per trip day carrying that day's plan in the description, and timed events for each scheduled item.
Always propose adding an all-day "Trip: <title>" event spanning the whole
trip, and useful reminders (online check-in opens, advance-booking
deadlines from the itinerary notes).
How to do it well
- Read
itinerary.mdas the source of truth; sync its current state, never a remembered one. - Time zones matter most here: create events in the destination's local time zone; flights use departure-airport local time for departure and arrival-airport local time for arrival. State the time zones used.
- Set sensible reminders: 3 hours before flights, 1 day before advance-booking deadlines, none for all-day summary events.
- Put booking references, addresses and links in the event description, and the venue address in the location field so maps work from the event.
- List the user's calendars first if they have several, and ask which to use.
Updates and changes
When the itinerary changes after a sync, offer to update the calendar too: find the existing events for the changed items and update rather than duplicate. If the trip is cancelled, offer to delete the trip's events — confirm before deleting anything.
Care points
- Create nothing without the traveller's go-ahead on the level of detail.
- Never store payment details in event descriptions; booking references are fine.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.