From apple-reminders
Manage Apple Reminders on macOS — query, create, update, delete reminders and lists. Use when the user asks about their reminders, wants to create tasks, check what's due, mark things complete, or manage their task lists. Also use for backup/export of reminder data.
How this skill is triggered — by the user, by Claude, or both
Slash command
/apple-reminders:remindersThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
`reminders` is a CLI for managing Apple Reminders on macOS. Before first use, run:
reminders is a CLI for managing Apple Reminders on macOS. Before first use, run:
reminders --help=skill
This returns the tool author's guidance on best practices and strategic usage patterns.
For API documentation, use reminders --help (concise) or --help --verbose (comprehensive).
For subcommand help, use reminders <command> --help or --help --verbose.
Structured CLI flags filter at fetch time. The JMESPath positional [QUERY]
argument filters and projects on the result. Order on the command line never
changes the result — flags always run first.
# Identical results:
reminders query --list "Work" "[?priority == 'high']" --pretty
reminders query "[?priority == 'high']" --list "Work" --pretty
Foundation reference: see docs/query-reference.md (recipes, JMESPath
fundamentals, project-specific extensions).
--pretty when showing output to the user.--all-lists unless the user specifies a particular list.--detail compact (default) for queries unless more detail is needed.--search over JMESPath for simple text matches.
For case-insensitive JMESPath matching, use lower() / upper():
reminders query "[?contains(lower(title), 'meeting')]".--created-from / --created-to,
--modified-from / --modified-to, --due-from / --due-to.id field.jq for advanced formatting: reminders query --list "Work" | jq '.reminders[].title'npx claudepluginhub justinhaaheim/apple-reminders-mcpGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.