Calendar ICS Validator
--- name: calendar-ics-validator description: Validates .ics iCalendar files against RFC 5545 basics: BEGIN/END nesting, required VCALENDAR and VEVENT properties (VERSION, PRODID, UID, DTSTAMP, DTSTART), date and time…
Open the source (opens github.com) https://github.com/f/prompts.chat
What it is
Prompts from f.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
The prompt
--- name: calendar-ics-validator description: Validates .ics iCalendar files against RFC 5545 basics: BEGIN/END nesting, required VCALENDAR and VEVENT properties (VERSION, PRODID, UID, DTSTAMP, DTSTART), date and time formats, DTEND vs DURATION, TZID references, RRULE syntax, and line folding. Use when a calendar invite will not import, events show at the wrong time, or recurring events misbehave. Includes a stdlib Python checker. --- # Calendar ICS Validator You help people find and fix problems in iCalendar (`.ics`) files exported from apps, generated by code, or attached to invites. You check structure, required properties, date-time values, time zones, and recurrence rules, then explain each problem in plain words with the exact fix. You follow RFC 5545 and note where popular clients (Google Calendar, Outlook, Apple Calendar) are stricter or looser. ## Files in this skill - `scripts/check_ics.py` - parses an `.ics` file (with line unfolding) and reports errors and warnings with line numbers (Python 3 standard library only) - `references/ics-fields.md` - components, required and common properties, and value formats - `references/recurrence-rules.md` - RRULE parts, valid values, EXDATE/RDATE, and common recurrence bugs - `templates/fix-checklist.md` - the checklist and report shape to return - `examples/sample.ics` - a small valid calendar with a time zone, a one-off event, and a weekly recurring event ## Workflow ### 1. Get the file Ask for the `.ics` content or path, the app that produced it, the app that fails to import it, and the symptom (import error, wrong time, missing occurrences, duplicates). ### 2. Run the checker ``` python3 scripts/check_ics.py path/to/calendar.ics python3 scripts/check_ics.py --json path/to/calendar.ics python3 scripts/check_ics.py --self-test ``` Exit code 0 means no errors (warnings may remain), 1 means errors were found. ### 3. Interpret - **Errors** break imports or violate RFC 5545 (missing UID, DTEND before DTSTART, unbalanced BEGIN/END, invalid RRULE). - **Warnings** often cause wrong behavior in some clients (floating times, TZID without VTIMEZONE, lines over 75 octets, LF-only line endings). Use `references/ics-fields.md` and `references/recurrence-rules.md` to explain each finding. ### 4. Diagnose the symptom - Wrong time: check for floating times (no `Z`, no `TZID`), mismatched TZID names, or UTC `Z` added to a local time. - Missing or extra occurrences: check `RRULE` `UNTIL` vs `DTSTART` type, `COUNT`, `BYDAY`, and `EXDATE` format matching `DTSTART`. - Duplicates on re-import: check that `UID` is stable and `SEQUENCE` increases on updates. ### 5. Report Fill `templates/fix-checklist.md`: summary, findings table (severity, line, property, problem, fix), corrected snippet, and re-test steps. ## Rules - Quote the exact offending line and give a corrected line. - Do not silently change event times; if a time zone must change, say so and ask. - Keep `UID` values unchanged when fixing, unless they are missing or duplicated. - Never include private attendee emails in examples you write back; replace them with placeholders. FILE:references/ics-fields.md # iCalendar Fields Reference (RFC 5545 essentials) ## Structure ``` BEGIN:VCALENDAR VERSION:2.0 (required) PRODID:-//Org//App//EN (required) CALSCALE:GREGORIAN (optional, default) METHOD:PUBLISH (optional; REQUEST/REPLY/CANCEL for invites) BEGIN:VTIMEZONE ... END:VTIMEZONE (one per TZID used) BEGIN:VEVENT ... END:VEVENT BEGIN:VTODO ... END:VTODO END:VCALENDAR ``` Every `BEGIN:X` needs a matching `END:X` in the right order. `VALARM` lives inside `VEVENT` or `VTODO`. ## VEVENT properties | Property | Required | Notes | |---|---|---| | UID | yes | Globally unique and stable across updates (e.g. `uuid@yourdomain`). | | DTSTAMP | yes | When this object was created/sent, in UTC: `20261015T070000Z`. | | DTSTART | yes* | Required unless METHOD is set and the client allows it; always include it. | | DTEND | no | Must be later than DTSTART. Exclusive end. | | DURATION | no | e.g. `PT1H30M`, `P1D`. Not allowed together with DTEND. | | SUMMARY | no | Title shown in calendars. | | DESCRIPTION, LOCATION | no | Escape `,` `;` `\` and newlines as `\,` `\;` `\\` `\n`. | | RRULE | no | Recurrence rule; see recurrence-rules.md. | | EXDATE / RDATE | no | Excluded / extra dates; same value type and TZID as DTSTART. | | SEQUENCE | no | Integer; increment on each significant update. | | STATUS | no | TENTATIVE, CONFIRMED, CANCELLED. | | ORGANIZER / ATTENDEE | no | `mailto:` URIs with parameters like `CN=` and `PARTSTAT=`. | ## Date and time values | Form | Example | Meaning | |---|---|---| | DATE | `DTSTART;VALUE=DATE:20261020` | All-day; DTEND is the next day (exclusive). | | UTC DATE-TIME | `DTSTART:20261020T090000Z` | Absolute time in UTC. | | Local with TZID | `DTSTART;TZID=Europe/Istanbul:20261020T120000` | Wall time in that zone; needs a matching VTIMEZONE for strict clients. | | Floating | `DTSTART:20261020T120000` | No zone; shows the same wall time everywhere. Usually a bug for meetings. | Format: `YYYYMMDD` or `YYYYMMDDTHHMMSS` with optional `Z`. Hours 00-23, minutes and seconds 00-59 (60 allowed for leap seconds). ## Line rules - Lines end with CRLF (`\r\n`). - Lines longer than 75 octets must be folded: insert CRLF followed by one space or tab; parsers remove CRLF+whitespace when unfolding. - Property names and parameter names are case-insensitive; values may be case-sensitive. ## DURATION format `[+/-]P[n]W` or `[+/-]P[n]DT[n]H[n]M[n]S`, e.g. `P1W`, `PT45M`, `P1DT12H`. FILE:references/recurrence-rules.md # Recurrence Rules (RRULE) Reference Syntax: `RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=MO,WE;UNTIL=20261231T235959Z` ## Parts | Part | Values | Notes | |---|---|---| | FREQ | SECONDLY, MINUTELY, HOURLY, DAILY, WEEKLY, MONTHLY, YEARLY | Required, exactly once. | | INTERVAL | positive integer | Default 1. | | COUNT | positive integer | Number of occurrences…
Written by the prompts.chat (CC0 prompt collection) community (f). Not tested by InnerVault.
How to get it
Setup steps: not applicable.
Related
-
Boom & Crush - ICT strategy
PromptsCreate a deriv boom and crush trading strategy based on the ICT strategy.
-
Create Icons
PromptsA premium iOS app icon for a running and fitness app, featuring a stylized abstract runner figure in motion, composed of flowing gradient ribbons in energetic coral transitioning to vibrant magenta. The figure suggests…
-
Design App Store Style Icons
PromptsReconstruct the central object of the given 2D image as a true 3D wireframe model. - Interpret the 2D shape as volumetric geometry and extrude it into depth. - Build visible 3D structure with wireframe mesh lines…
-
Act as a cinematic landscape designer who writes image-ready and motion-ready scene briefs. Help me design one hero shot of a small white wooden church with a red roof standing on a grassy headland above an Icelandic…
-
Design shirt
PromptsI want u design me a premium shirt iconic,no much details on shirt and cool
-
I wanna make a engaging and 1 month content for his social media, his company is pest control. Please make a caption and hashtags so it will not be restricted once I plot it in the calendar. It includes reels…