How do I install the Eventkit skill?

Run npx skillmds@latest add caglarbaranbora/eventkit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Eventkit safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Eventkit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Eventkit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Eventkit?

caglarbaranbora (@caglarbaranbora) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Eventkit by caglarbaranbora — Agent Skill

Name: Eventkit
Author: caglarbaranbora

Eventkit

Route EventKit implementation tasks to the correct Knowledge Contracts -- authorization and access levels, event CRUD and fetch predicates, reminder CRUD and fetch, and recurrence rules with the EventKitUI hand-off decision. Use when checking EKAuthorizationStatus, calling requestFullAccessToEvents(completion:)/requestWriteOnlyAccessToEvents(completion:)/requestFullAccessToReminders(completion:)/requestAccess(to:completion:), declaring NSCalendarsUsageDescription/NSCalendarsFullAccessUsageDescription/NSCalendarsWriteOnlyAccessUsageDescription/NSRemindersUsageDescription/NSRemindersFullAccessUsageDescription, creating/saving/removing an EKEvent or EKReminder, building predicateForEvents(withStart:end:calendars:)/predicateForReminders(in:), calling events(matching:)/fetchReminders(matching:completion:), constructing EKRecurrenceRule/EKRecurrenceEnd, or deciding between EKEventEditViewController/EKEventViewController and custom UI. v1 is calendar/reminder access through EKEventStore only -- no EKSource/multi-acc

File contents

EventKit — Foundations Skill

Purpose

Route EventKit implementation tasks to the minimum required EventKit Knowledge Contracts. v1 scope is calendar and reminder access through EKEventStore -- authorization, event/reminder CRUD, fetch predicates, recurrence rules, and the point where a custom-UI feature should instead hand off to EventKitUI's prebuilt view controllers -- not multi-account calendar-source management, not CalDAV/Exchange specifics, not live external-change syncing, and not EventKit inside a widget extension.

Routing

Load only the contracts relevant to the task. All paths relative to knowledge/eventkit/.

Checking EKAuthorizationStatus; calling requestFullAccessToEvents(completion:)/requestWriteOnlyAccessToEvents(completion:)/requestFullAccessToReminders(completion:)/the legacy requestAccess(to:completion:); or declaring the matching Info.plist usage-description key -> authorization-and-access-levels.md
Creating/saving/removing an EKEvent (EKEvent(eventStore:), save(_:span:commit:), remove(_:span:commit:)); choosing a calendar via defaultCalendarForNewEvents; or building/running predicateForEvents(withStart:end:calendars:) + events(matching:) -> event-crud-and-fetch-predicates.md
Creating/saving/removing an EKReminder (EKReminder(eventStore:), save(_:commit:), remove(_:commit:)); or building/running predicateForReminders(in:) + the asynchronous fetchReminders(matching:completion:) -> reminder-crud-and-fetch.md
Constructing EKRecurrenceRule/EKRecurrenceEnd; or deciding between EKEventEditViewController/EKEventViewController (EventKitUI) and custom UI built on the CRUD contracts -> recurrence-rules-and-eventkitui-handoff.md

Never load more than the contracts relevant to the specific question.

Stop Conditions

Stop and report if the requested topic has no matching Knowledge Contract in knowledge/eventkit/ — do not guess or fall back to general knowledge. EKSource / multi-account calendar-source management as its own deep topic is out of scope entirely -- mentioned only in passing, where relevant to choosing a calendar to save to, inside the CRUD contracts; not planned as a separate contract. CalDAV/Exchange server-specific behavior is out of scope entirely. The EKEventStoreChanged notification and live external-change syncing are out of scope entirely -- not yet built (see docs/architecture/domain-map.md). EventKit usage inside a widget extension is widgetkit's job, not this Skill's -- report that boundary explicitly rather than routing to a contract here.

---name: eventkitdescription: Route EventKit implementation tasks to the correct Knowledge Contracts -- authorization and access levels, event CRUD and fetch predicates, reminder CRUD and fetch, and recurrence rules with the EventKitUI hand-off decision. Use when checking EKAuthorizationStatus, calling requestFullAccessToEvents(completion:)/requestWriteOnlyAccessToEvents(completion:)/requestFullAccessToReminders(completion:)/requestAccess(to:completion:), declaring NSCalendarsUsageDescription/NSCalendarsFullAccessUsageDescription/NSCalendarsWriteOnlyAccessUsageDescription/NSRemindersUsageDescription/NSRemindersFullAccessUsageDescription, creating/saving/removing an EKEvent or EKReminder, building predicateForEvents(withStart:end:calendars:)/predicateForReminders(in:), calling events(matching:)/fetchReminders(matching:completion:), constructing EKRecurrenceRule/EKRecurrenceEnd, or deciding between EKEventEditViewController/EKEventViewController and custom UI. v1 is calendar/reminder access through EKEventStore only -- no EKSource/multi-acc---# EventKit — Foundations Skill## PurposeRoute EventKit implementation tasks to the minimum required EventKitKnowledge Contracts. v1 scope is calendar and reminder access through`EKEventStore` -- authorization, event/reminder CRUD, fetch predicates,recurrence rules, and the point where a custom-UI feature should insteadhand off to EventKitUI's prebuilt view controllers -- not multi-accountcalendar-source management, not CalDAV/Exchange specifics, not liveexternal-change syncing, and not EventKit inside a widget extension.## RoutingLoad only the contracts relevant to the task. All paths relative toknowledge/eventkit/.- Checking `EKAuthorizationStatus`; calling `requestFullAccessToEvents(completion:)`/`requestWriteOnlyAccessToEvents(completion:)`/`requestFullAccessToReminders(completion:)`/the legacy `requestAccess(to:completion:)`; or declaring the matching Info.plist usage-description key -> authorization-and-access-levels.md- Creating/saving/removing an `EKEvent` (`EKEvent(eventStore:)`, `save(_:span:commit:)`, `remove(_:span:commit:)`); choosing a calendar via `defaultCalendarForNewEvents`; or building/running `predicateForEvents(withStart:end:calendars:)` + `events(matching:)` -> event-crud-and-fetch-predicates.md- Creating/saving/removing an `EKReminder` (`EKReminder(eventStore:)`, `save(_:commit:)`, `remove(_:commit:)`); or building/running `predicateForReminders(in:)` + the asynchronous `fetchReminders(matching:completion:)` -> reminder-crud-and-fetch.md- Constructing `EKRecurrenceRule`/`EKRecurrenceEnd`; or deciding between `EKEventEditViewController`/`EKEventViewController` (EventKitUI) and custom UI built on the CRUD contracts -> recurrence-rules-and-eventkitui-handoff.mdNever load more than the contracts relevant to the specific question.## Stop ConditionsStop and report if the requested topic has no matching Knowledge Contractin knowledge/eventkit/ — do not guess or fall back to general knowledge.`EKSource` / multi-account calendar-source management as its own deeptopic is out of scope entirely -- mentioned only in passing, whererelevant to choosing a calendar to save to, inside the CRUD contracts;not planned as a separate contract. CalDAV/Exchange server-specificbehavior is out of scope entirely. The `EKEventStoreChanged` notificationand live external-change syncing are out of scope entirely -- not yetbuilt (see docs/architecture/domain-map.md). EventKit usage inside awidget extension is `widgetkit`'s job, not this Skill's -- report thatboundary explicitly rather than routing to a contract here.

Frequently asked questions