calendar-stats
Show calendar statistics — meeting volume, hours in meetings, busiest days, top calendars, and meeting load by day of week. Use when user asks how many meetings they have, how busy they are, or wants a time audit.
npx skills add majiayu000/claude-skill-registry --skill calendar-stats --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Calendar Stats — Meeting Volume and Time Audit Show meeting statistics for a time period. ## Arguments `$ARGUMENTS` — time range (default: last 30 days): - "last week", "this month", "last 90 days" - "2026-01-01 to 2026-03-01" → date range - Empty → last 30 days ## Steps ```bash DB="$HOME/Library/Group Containers/group.com.apple.calendar/Calendar.sqlitedb" ARGS="$ARGUMENTS" DAYS=30 if echo "$ARGS" | grep -qiE '[0-9]+ day'; then DAYS=$(echo "$ARGS" | grep -oiE '[0-9]+' | head -1); fi if echo "$ARGS" | grep -qi 'week'; then DAYS=7; fi if echo "$ARGS" | grep -qi '90'; then DAYS=90; fi START_CD=$(( $(date +%s) - DAYS * 86400 - 978307200 )) END_CD=$(( $(date +%s) - 978307200 )) echo "=== OVERVIEW ===" sqlite3 "$DB" " SELECT COUNT(DISTINCT ci.ROWID) as total_events, SUM(CASE WHEN ci.all_day = 0 THEN MAX(0, MIN(COALESCE(oc.occurrence_end_date, oc.occurrence_date + 3600), COALESCE(oc.occurrence_start_date, oc.occurrence_date) + 86400) - COALESCE(oc.occurrence_start_date, oc.occurrence_date)) ELSE 0 END) / 3600.0 as total_hours, COUNT(DISTINCT CASE WHEN ci.has_attendees = 1 THEN ci.ROWID END) as meetings_with_others, COUNT(DISTINCT CASE WHEN ci.all_day = 1 THEN ci.ROWID END) as all_day_ev
- Arguments
- Steps
- Output Format
if echo "$ARGS" | grep -qiE '[0-9]+ day'; then DAYS=$(echo "$ARGS" | grep -oiE '[0-9]+' | head -1); fi if echo "$ARGS" | grep -qi 'week'; then DAYS=7; fi if echo "$ARGS" | grep -qi '90'; then DAYS=90; fi echo "=== OVERVIEW ===" sqlite3 "$DB" " SELECT ELSE 0 END) / 3600.0 as total_hours, FROM OccurrenceCache oc JOIN CalendarItem ci ON oc.event_id = ci.ROWID LEFT JOIN Store s ON (SELECT store_id FROM Calendar WHERE ROWID = ci.calendar_id)
What does the calendar-stats skill do?
Show calendar statistics — meeting volume, hours in meetings, busiest days, top calendars, and meeting load by day of week. Use when user asks how many meetings they have, how busy they are, or wants a time audit.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill calendar-stats --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.