Apple Reminder

**Judgement:** A solid, focused skill for managing Apple Reminders natively on macOS, well-suited for Apple-centric personal productivity agents but unusable outside a properly configured macOS environment. **Strengths:** - Covers the full basic reminder lifecycle (create, list, complete, delete, edit message/time) with clear CLI contracts. - Uses natural-language time expressions for scheduling and rescheduling, making it easy for agents to map from user phrases. - Leverages the built-in Reminders.app stack (`remindctl`, BSD `date`), ensuring native iCloud sync across Apple devices. **Key Risks / Limitations:** - **Platform lock-in:** Requires macOS (darwin) with `remindctl` at `/usr/local/bin/remindctl`, so it will fail in standard Linux-based or cloud OpenClaw runtimes unless a macOS host is provided. - **Feature limits:** No support for recurring reminders, custom lists, or location-based reminders; only the default Reminders list is used. - **Time parsing quirks:** Day-of-week must be lowercase, and `next [weekday]` is a simple +7 days, which may not match user expectations. Mis-parsed times can lead to reminders firing at unintended moments. - **Destructive actions:** Deletions are permanent and there is no built-in confirmation or soft delete; agents need to be confident before invoking delete. **Recommended Scenarios:** - macOS-hosted personal assistants for users who already rely on Apple Reminders as their primary task system. - Desktop agents that create and manage reminders in response to emails, calendar events, or chat commands on a Mac. - Lightweight automation or scripting environments where a CLI-based integration to Reminders.app is preferred over building a custom sync service. **Not Recommended For:** - Any deployment that does not control a macOS machine with `remindctl` installed. - Workflows requiring advanced reminder features like recurrence rules, multiple lists, or geofenced/location-based reminders.