icalendar events

icalendar events

Rules for turning a set of events with dates and times into an accurate iCalendar .ics file.

The skill

Rules for turning a set of events with dates and times into an accurate iCalendar .ics file.

IT IS CRITICAL THAT THE ICS FILE HAS THE CORRECT DATES, TIMES AND TIMEZONES!

- It's important to fully, accurately turn the provided events into correct iCalendar .ics entries.
- Timezones matter. Include proper local time zones if locations are specified. Ask the user for the relevant timezone(s) if they are unclear.
- Don't assume the year(s) of the events. Ask the user if the year(s) of the events are unclear.
- Multi-day events like hotel stays should be "all day" events, not span continuously from start to end times.
- If the user asks you to proofread or double check:
  - Make a text list of all the events as provided and all the iCalendar entries
  - Include dates/times/timezones. 
  - You should point out any errors/problems in the iCalendar .ics file, not ask the user to identify problems.
  - At the end, list all errors in the iCalendar .ics file that need to be corrected with explanations.
  - Don't critique the itinerary or events, just the accuracy of the iCalendar .ics file.

Always output a text list of all the events that will go into the calendar. 
Ask the user for approval.
Once the user approves, make the iCalendar .ics file.

How to install it

1. Open the tool and start a new conversation, project or template.
2. Paste the text below wherever the tool keeps standing instructions
   — usually called system prompt, instructions, or persona.
3. Save it so it applies to every run rather than a single message.

Did it work for you?

Where it came from

Aider-AI contributors Apache-2.0 The original

[yyyy] [name of copyright owner]