Best fit
Calendar invites can render at the wrong time or span the wrong day when DTSTART, DTEND, TZID, VALUE=DATE, sequence, or recurrence evidence disagree.
// Productivity
Calendar Invite Timezone Preflight
Check normalized iCalendar events for floating times, DATE mismatches, missing boundaries, sequence errors, and recurrence evidence.
What problem does Calendar Invite Timezone Preflight solve?
Calendar invites can render at the wrong time or span the wrong day when DTSTART, DTEND, TZID, VALUE=DATE, sequence, or recurrence evidence disagree.
Use it to
- Preflight a generated ICS invite.
- Find floating DATE-TIME values.
- Review all-day and recurring event evidence before distribution.
What it returns
- findings.csv with stable codes and record identifiers
- review-manifest.csv with every reviewed item
- result.json with READY, REVIEW, or BLOCK gate
- report.md with a human-readable decision handoff
A representative input and result
input {"events":[{"uid":"event-1","dtstart":"20260801T140000Z","dtend":"20260801T150000Z","value_type":"DATE-TIME","sequence":0}]}
result READY; UTC event boundaries and sequence evidence reviewed.
Access and approval boundaries
- Read access to one user-supplied local JSON evidence file.
- Write access only to the selected local output directory.
- No browser, network, credential, account, environment-variable, or external-action permission.
Known limitations
- Version 1 checks normalized core properties, not full client-specific rendering.
- It does not expand complex recurrence rules or import an invite.
- A passing result does not establish identical behavior across calendar clients.
// choose with context
Is Calendar Invite Timezone Preflight the right skill?
It returns
findings.csv with stable codes and record identifiers. review-manifest.csv with every reviewed item.
Do not use it as
Version 1 checks normalized core properties, not full client-specific rendering.
Compatibility, access, version, and licence
- Reads or accesses
- Declared local scope: one owner-selected local JSON input, one owner-selected local output directory.
- Compatibility
- Normalized UTF-8 JSON input documented in the package. Python 3.10 or newer on Windows, macOS, or Linux. Local files only; no live account or provider connection.
- Version
- 1.0.0
- Licence
- Review the package licence and seller terms at the linked destination.
Questions
Does it change or upload anything?
No. It reads supplied local evidence and writes only to the selected output directory.
Is this an AI judgment?
No. The packaged checker is deterministic and applies documented rules to the supplied input.
What does a ready result mean?
It means no automated finding was produced. The responsible owner still reviews the original source and decides what to do.
How does malformed input behave?
Invalid JSON, duplicate identifiers, missing required arrays, and invalid core values fail closed.
Can I audit the result?
Yes. Every finding carries a stable code, record identifier, severity, source, and message.
Calendar Invite Timezone Preflight keeps proof and approval boundaries visible.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get Calendar Invite Timezone Preflight on Agensi