calendar-recurring
Skill7 starsChanged 9 months agoMITView on GitHub
List all recurring meetings and meeting series. Use when user asks about standing meetings, recurring events, weekly syncs, or wants to see their regular meeting cadence.
In this repository32 other files it gives its agents.
- calendar-accountsSkill
- calendar-attendeesSkill
- calendar-conflictsSkill
- calendar-coreSkill
- calendar-eventSkill
- calendar-freeSkill
- calendar-searchSkill
- calendar-statsSkill
- calendar-todaySkill
- calendar-upcomingSkill
- mail-accountsSkill
- mail-action-itemsSkill
- mail-attachmentsSkill
- mail-bankingSkill
- mail-contactsSkill
- mail-coreSkill
- mail-digestSkill
- mail-expensesSkill
- mail-fromSkill
- mail-meetingsSkill
- mail-needs-replySkill
- mail-newsletterSkill
- mail-readSkill
- mail-searchSkill
- mail-securitySkill
- mail-statsSkill
- mail-subscriptionsSkill
- mail-threadSkill
- mail-top-sendersSkill
- mail-travelSkill
- mail-triageSkill
- mail-workSkill
The file
Files
Calendar Recurring — Standing Meetings and Series
List all active recurring events, grouped by frequency.
Arguments
$ARGUMENTS — optional filter:
- Empty → all recurring events
"weekly"→ only weekly recurring"standup"→ search by name
Steps
DB="$HOME/Library/Group Containers/group.com.apple.calendar/Calendar.sqlitedb"
FILTER="$ARGUMENTS"
NOW_CD=$(( $(date +%s) - 978307200 ))
KEYWORD_FILTER=""
if [ -n "$FILTER" ] && ! echo "$FILTER" | grep -qiE '^(weekly|daily|monthly|yearly)$'; then
KEYWORD_FILTER="AND ci.summary LIKE '%${FILTER}%'"
fi
FREQ_FILTER=""
case "$(echo $FILTER | tr '[:upper:]' '[:lower:]')" in
daily) FREQ_FILTER="AND r.frequency = 1" ;;
weekly) FREQ_FILTER="AND r.frequency = 2" ;;
monthly) FREQ_FILTER="AND r.frequency = 3" ;;
yearly) FREQ_FILTER="AND r.frequency = 4" ;;
esac
sqlite3 -separator '|' "$DB" "
SELECT
ci.summary as title,
CASE r.frequency
WHEN 1 THEN 'Daily'
WHEN 2 THEN 'Weekly'
WHEN 3 THEN 'Monthly'
WHEN 4 THEN 'Yearly'
ELSE 'Unknown'
END as freq,
r.interval as every_n,
COALESCE(
strftime('%H:%M', oc_next.occurrence_start_date + 978307200, 'unixepoch', 'localtime'),
strftime('%H:%M', oc_next.occurrence_date + 978307200, 'unixepoch', 'localtime')
) as time_of_day,
date(oc_next.occurrence_date + 978307200, 'unixepoch', 'localtime') as next_occurrence,
COALESCE(l.title, '') as location,
COALESCE(ci.conference_url, '') as conf_url,
c.title as calendar,
ci.has_attendees,
ci.ROWID as id
FROM CalendarItem ci
JOIN Recurrence r ON r.owner_id = ci.ROWID
LEFT JOIN (
SELECT event_id, MIN(occurrence_date) as occurrence_date, occurrence_start_date
FROM OccurrenceCache
WHERE occurrence_date >= $NOW_CD
GROUP BY event_id
) oc_next ON oc_next.event_id = ci.ROWID
LEFT JOIN Calendar c ON ci.calendar_id = c.ROWID
LEFT JOIN Store s ON c.store_id = s.ROWID
LEFT JOIN Location l ON ci.location_id = l.ROWID
WHERE ci.hidden = 0
AND ci.status != 2
AND s.type != 5
AND s.disabled = 0
AND oc_next.occurrence_date IS NOT NULL
$FREQ_FILTER
$KEYWORD_FILTER
ORDER BY r.frequency, r.interval, COALESCE(oc_next.occurrence_start_date, oc_next.occurrence_date);
"Output Format
Group by frequency:
Daily (N)
- [time] Title — Every N days — [location/video]
Weekly (N)
- [time] Title — Every week — [calendar]
- [time] Title — Every 2 weeks (biweekly)
Monthly (N)
- [time] Title — Monthly
Show has_attendees flag so user knows which are solo vs. group meetings.
Note next occurrence date for each.
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.

