calendar-recurring

You can list recurring calendar events by running a Bash workflow that queries Calendar.sqlite via sqlite3. It filters by frequency or keyword and outputs structured data including title, cadence, interval, next occurrence, and conference URL.

Yes, you can filter standing meetings by frequency. The workflow supports ARGUMENTS filtering by daily, weekly, monthly, or yearly frequencies, allowing you to isolate specific recurring event series from your calendar data.

Viewing recurring calendar events via sqlite3 outputs structured data fields including title, frequency, interval, time_of_day, next_occurrence, location, conference_url, calendar, has_attendees, and id for comprehensive scheduling analysis.

Yes, this approach works without external dependencies. It relies on a Bash-based workflow utilizing sqlite3 to directly read the local Calendar.sqlite file, requiring no additional packages or components to extract recurring event data.

To find conflicts between weekly standups, you can inventory all active recurring events and series grouped by frequency. Computing next occurrences and time of day allows you to quickly identify overlapping schedules across calendars.

The best way to inventory recurring calendar series without manual sorting is querying Calendar.sqlite with sqlite3. This automatically computes next occurrences and groups active recurring events by frequency for structured conflict resolution.