메뉴
Add events to iCloud calendar by writing .ics files and triggering vdirsyncer sync. Use when user asks to 'add to calendar', 'create an event', 'schedule X on Tuesday', 'put this on the calendar', or any request to create a calendar event.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create and schedule CrossFit workouts on Garmin Connect. Use when user asks to 'create a CrossFit workout', 'make a WOD', 'build an EMOM', 'schedule a CrossFit session', 'AMRAP workout', 'Tabata', 'for time workout', or any request to create a non-running workout for Garmin.
This skill should be used when the user asks to 'design a feature', 'evaluate approaches', 'plan the architecture', 'domain modeling', 'DDD design', 'bounded contexts', 'functional core imperative shell', 'how should I structure this', 'what pattern should I use', or needs upfront architectural design for Java/Spring Boot, TypeScript/Next.js, or Rust codebases. For DESIGN decisions before implementation - not for reviewing existing code (use the architecture-agent via /review-pr for that).
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
This skill should be used when the user asks to 'implement', 'write code', 'build a feature', 'create a function', 'add functionality', 'code this', 'make this work', or needs to write production code for Java/Spring Boot or TypeScript/Next.js following FP, DDD, and testability patterns. Ensures code follows functional core/imperative shell, proper invariants, Either-based error handling, and is designed for testing without mocks.
This skill should be used when the user asks to 'check spec alignment', 'verify requirements coverage', 'detect drift', 'spec audit', or automatically at wave gates. Verifies implementation aligns with specification - different from code review which checks quality.
This skill should be used when the user asks to 'specify a feature', 'write requirements', 'define what we're building', 'capture requirements', 'document the spec', or before invoking /architecture-tech-lead for non-trivial features. Produces formal specifications (WHAT/WHY) that feed into architecture and planning phases.
| name | calendar-add |
| description | Add events to iCloud calendar by writing .ics files and triggering vdirsyncer sync. Use when user asks to 'add to calendar', 'create an event', 'schedule X on Tuesday', 'put this on the calendar', or any request to create a calendar event. |
| allowed-tools | Read, Bash, Write, Glob |
Creates calendar events by writing .ics files to the local vdirsyncer-synced iCloud calendar directory, then triggering a sync to push to iCloud.
~/.local/share/calendars/icloud/D8C2180E-3AD0-406E-9B55-23DA5F2CC674/Europe/Copenhagensystemctl --user start vdirsyncer-sync.serviceParse $ARGUMENTS or conversational context for:
Use the current date ({{date}} or system date) as reference. Always resolve forward:
Compute the actual date as YYYYMMDD format for the .ics file.
Generate a unique UID for each event using uuidgen (uppercase).
BEGIN:VCALENDAR
CALSCALE:GREGORIAN
PRODID:-//reclaw//calendar-add//EN
VERSION:2.0
BEGIN:VEVENT
CREATED:${NOW_UTC}
DTEND;TZID=Europe/Copenhagen:${END_DATE}T${END_TIME}00
DTSTAMP:${NOW_UTC}
DTSTART;TZID=Europe/Copenhagen:${START_DATE}T${START_TIME}00
LAST-MODIFIED:${NOW_UTC}
SEQUENCE:0
SUMMARY:${TITLE}${LOCATION_LINE}
UID:${UUID}
TRANSP:OPAQUE
END:VEVENT
BEGIN:VTIMEZONE
TZID:Europe/Copenhagen
BEGIN:DAYLIGHT
DTSTART:19810329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:19961027T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
END:VTIMEZONE
END:VCALENDAR
For events without a specific time, use VALUE=DATE format:
DTSTART;VALUE=DATE:${START_DATE}
DTEND;VALUE=DATE:${END_DATE_PLUS_ONE}
Note: All-day event DTEND is the day AFTER the last day (exclusive). A single all-day event on March 5th has DTEND March 6th.
| Variable | Format | Example |
|---|---|---|
NOW_UTC | YYYYMMDDTHHmmssZ | 20260301T143000Z |
START_DATE | YYYYMMDD | 20260303 |
START_TIME | HHmmss | 180000 |
END_DATE | YYYYMMDD | 20260303 |
END_TIME | HHmmss | 190000 |
TITLE | Plain text | Dinner at mom's |
LOCATION_LINE | \nLOCATION:${place} or empty | \nLOCATION:Cafe Noir |
UUID | Uppercase UUID | A1B2C3D4-E5F6-... |
uuidgen | tr '[:lower:]' '[:upper:]'~/.local/share/calendars/icloud/D8C2180E-3AD0-406E-9B55-23DA5F2CC674/${UUID}.ics
After writing the .ics file, trigger an immediate sync:
systemctl --user start vdirsyncer-sync.service
This is fire-and-forget. The sync service handles the push to iCloud. If the service isn't running, the event will sync on the next timer cycle (every 15 minutes).
After creating the event, confirm with a concise summary:
Added to J & P calendar:
[Title]
[Day name], [Date] [Time range or "all day"]
[Location if set]
Syncing to iCloud...
uuidgen isn't available, generate a UUID-like string with: python3 -c "import uuid; print(str(uuid.uuid4()).upper())"Input: "add dentist appointment this Tuesday at 14:30"
Input: "put dinner at mom's on Saturday evening"
Input: "calendar: vacation March 10-15"
Input: "add meeting with Lars tomorrow 10am for 90 minutes at the office"