Menu
Apple Reminders via remindctl: add, list, complete.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | apple-rmndrs |
| description | Apple Reminders via remindctl: add, list, complete. |
| version | 1.0.0 |
| author | Hermes Agent |
| license | MIT |
| platforms | ["macos"] |
| metadata | {"hermes":{"tags":["Reminders","tasks","todo","macOS","Apple"]}} |
| prerequisites | {"commands":["remindctl"]} |
Use remindctl to manage Apple Reminders directly from the terminal. Tasks sync across all Apple devices via iCloud.
brew install steipete/tap/remindctlremindctl status / Request: remindctl authorizeremindctl # Today's reminders
remindctl today # Today
remindctl tomorrow # Tomorrow
remindctl week # This week
remindctl overdue # Past due
remindctl all # Everything
remindctl 2026-01-04 # Specific date
remindctl list # List all lists
remindctl list Work # Show specific list
remindctl list Projects --create # Create list
remindctl list Work --delete # Delete list
remindctl add "Buy milk"
remindctl add --title "Call mom" --list Personal --due tomorrow
remindctl add --title "Meeting prep" --due "2026-02-15 09:00"
remindctl complete 1 2 3 # Complete by ID
remindctl delete 4A83 --force # Delete by ID
remindctl today --json # JSON for scripting
remindctl today --plain # TSV format
remindctl today --quiet # Counts only
Accepted by --due and date filters:
today, tomorrow, yesterdayYYYY-MM-DDYYYY-MM-DD HH:mm2026-01-04T12:34:56Z)--json for programmatic parsingUse when defining new features, product behavior, UI/component design, architecture choices, contract changes, or ambiguous medium/high-complexity work before implementation.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.
Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when strict TDD is explicitly requested, or when an approved atomic implementation task has already chosen TDD Route strict.