Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
terrylica avatar

Calendar Event Manager

  • 199 installs
  • 62 repo stars
  • Updated August 3, 2026
  • terrylica/cc-skills

Use calendar-event-manager for development tasks

About

calendar-event-manager: A skill for development. This provides functionality for development workflows.

  • calendar-event-manager

Calendar Event Manager by the numbers

  • 199 all-time installs (skills.sh)
  • +1 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #2,000 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/terrylica/cc-skills --skill calendar-event-manager

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs199
repo stars62
Last updatedAugust 3, 2026
Repositoryterrylica/cc-skills

What it does

Use calendar-event-manager for development tasks

Files

SKILL.mdMarkdownGitHub ↗

Calendar Event Manager

Create macOS Calendar events with tiered sound alarms and paired Reminders so events are never missed across Mac and iOS.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

CRITICAL RULES (Hard-Learned Truths 2026-02-12)

These rules are NON-NEGOTIABLE. Violating any of them defeats the purpose of this skill.

1. Calendar + Reminders ALWAYS Together

Every event MUST create BOTH:

  • Calendar event with multiple sound alarm entries (custom sound per tier)
  • Reminders (3 minimum) as a separate notification channel

Never create one without the other.

2. Use sound alarm, NOT display alarm

-- CORRECT: audible alert with custom sound
make new sound alarm at end of sound alarms with properties {trigger interval:-60, sound name:"Glass"}

-- WRONG: silent visual banner only
make new display alarm at end of display alarms with properties {trigger interval:-60}

Each alarm supports its own sound name property. Use DIFFERENT sounds for different tiers so the user knows which alert level it is by sound alone.

3. ONLY Long Sounds (>= 1.4 seconds)

Short sounds get missed and ignored. NEVER use sounds under 1.4 seconds.

APPROVED sounds only:

SoundDurationUse For
Funk2.16sAt event time (loudest)
Glass1.65s1 hour before
Pop1.63sMorning-of / 3 hrs before
Sosumi1.54sDay-before
Ping1.50s30 min before
Submarine1.49sAlternative
Blow1.40sGentle early reminder

BANNED sounds: Hero, Basso, Bottle, Purr, Frog, Morse, Tink (all < 1.4s)

4. Multiple Early Reminders Are Mandatory

Minimum alarm tiers for any event:

TierTriggerCalendar SoundReminder
1 day before-1440 minBlow"TOMORROW: ..."
Morning-of 9 AMAbsoluteSosumi"TODAY: ..."
3 hours before-180 minPop(via Calendar)
1 hour before-60 minGlass(via Calendar)
30 min before-30 minPing(via Calendar)
At event time0 minFunkDue-time reminder

5. macOS Notification Settings Prerequisite

Calendar notifications must be enabled in System Settings:

  • System Settings > Notifications > Calendar > Allow Notifications = ON
  • Alert style = Banners or Alerts
  • Play sound = ON

Open with: open "x-apple.systempreferences:com.apple.Notifications-Settings.extension"

---

TodoWrite Task Templates

Template A: Create Event from Invitation

1. Extract event details (title, date, time, location, notes, RSVP)
2. Create Calendar event with 6-tier sound alarms (Blow, Sosumi, Pop, Glass, Ping, Funk)
3. Create 3 Reminders (TOMORROW, TODAY morning, due-time)
4. Verify event and reminders created
5. Report full schedule to user

Template B: Create Event from User Description

1. Ask user for: event name, date/time, duration, location
2. Create Calendar event with 6-tier sound alarms
3. Create 3 Reminders
4. Verify event and reminders created
5. Report full schedule to user

Template C: Test Notification Setup

1. Create test Calendar event 3 min in future with sound alarms (1 min, 2 min tiers)
2. Create test Reminder 2 min in future
3. Wait for user confirmation of notifications
4. Clean up test event and reminders

---

AppleScript Date Construction (CRITICAL)

NEVER use `date "STRING"` in AppleScript. String-based date parsing is locale-dependent and silently produces wrong results:

Anti-patternWhat happensExample
date "April 1, 2026 at 6:00:00 PM"On 24h systems, "PM" is ignored → 06:004 failures in amonic session
date "2026-04-01 18:00:00"ISO parsed as individual numbers → year 121691 failure
set month before set day to 1Day 31 + April (30 days) → rolls to May 11 failure

ALWAYS use programmatic date construction:

-- Build date safely: day-first-then-month prevents rollover
set d to current date
set day of d to 1           -- safe floor FIRST (prevents month rollover)
set month of d to April
set year of d to 2026
set day of d to 1           -- now set actual target day
set hours of d to 18        -- 24h format, no AM/PM ambiguity
set minutes of d to 0
set seconds of d to 0

Calendar Discovery (run first)

tell application "Calendar"
    set output to ""
    repeat with c in calendars
        set output to output & name of c & " (writable:" & writable of c & ")" & linefeed
    end repeat
    output
end tell

Use the first writable:true calendar. Never assume "Home" or "Calendar" exists.

Full Event Creation (Copy-Paste Ready)

tell application "Calendar"
    -- Build start date programmatically
    set startDate to current date
    set day of startDate to 1
    set month of startDate to MONTH_CONSTANT
    set year of startDate to YEAR_INT
    set day of startDate to DAY_INT
    set hours of startDate to HOUR_24
    set minutes of startDate to 0
    set seconds of startDate to 0

    -- Build end date (1 hour later)
    set endDate to startDate + 1 * hours

    tell calendar "WRITABLE_CALENDAR_NAME"
        set newEvent to make new event with properties {summary:"EVENT_NAME", start date:startDate, end date:endDate, location:"LOCATION", description:"NOTES"}
        tell newEvent
            make new sound alarm at end of sound alarms with properties {trigger interval:-1440, sound name:"Blow"}
            make new sound alarm at end of sound alarms with properties {trigger interval:-180, sound name:"Pop"}
            make new sound alarm at end of sound alarms with properties {trigger interval:-60, sound name:"Glass"}
            make new sound alarm at end of sound alarms with properties {trigger interval:-30, sound name:"Ping"}
            make new sound alarm at end of sound alarms with properties {trigger interval:0, sound name:"Funk"}
        end tell
    end tell
    reload calendars
end tell

Verification (always run after creation)

tell application "Calendar"
    tell calendar "WRITABLE_CALENDAR_NAME"
        set matches to (every event whose summary is "EVENT_NAME" and start date > (current date))
        repeat with e in matches
            log (summary of e) & " | " & (start date of e) & " → " & (end date of e)
        end repeat
    end tell
end tell

Paired Reminders Creation

tell application "Reminders"
    set defaultList to default list

    -- Build date programmatically (same pattern as Calendar)
    set eventDate to current date
    set day of eventDate to 1
    set month of eventDate to MONTH_CONSTANT
    set year of eventDate to YEAR_INT
    set day of eventDate to DAY_INT
    set hours of eventDate to HOUR_24
    set minutes of eventDate to 0
    set seconds of eventDate to 0

    -- Due-time reminder
    make new reminder in defaultList with properties {name:"EVENT_NAME", due date:eventDate, body:"LOCATION\nNOTES"}
    -- Day-before
    make new reminder in defaultList with properties {name:"TOMORROW: EVENT_NAME", due date:(eventDate - 1 * days), body:"Event tomorrow! LOCATION"}
    -- Morning-of at 9 AM
    set morningDate to eventDate
    set hours of morningDate to 9
    set minutes of morningDate to 0
    make new reminder in defaultList with properties {name:"TODAY: EVENT_NAME", due date:morningDate, body:"Today! LOCATION"}
end tell

---

Post-Change Checklist

After modifying this skill:

1. [ ] Sound reference table matches sound-reference.md 2. [ ] All 6 alarm tiers documented with correct sounds 3. [ ] BANNED sounds list is complete 4. [ ] Hook file (hooks/calendar-reminder-sync.ts) aligned with skill rules 5. [ ] AppleScript examples use sound alarm not display alarm

---

References

Post-Execution Reflection

After this skill completes, check before closing:

1. Did the command succeed? — If not, fix the instruction or error table that caused the failure. 2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match. 3. Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.

Related skills

Backend & APIsbackendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.