automating-reminders
Automates Apple Reminders using JavaScript for Automation (JXA). Use when asked to "create reminders programmatically", "automate reminder lists", "JXA Reminders scripting", or "manage reminders via automation". Covers list/reminder management, filtering with 'whose' queries, efficient creation via constructors and push operations, and copy-delete patterns for moving items.
What this skill does
# Automating Reminders (JXA-first, AppleScript discovery)
## Relationship to the macOS automation skill
- Standalone for Reminders; reuse `automating-mac-apps` for permissions, shell helpers, and ObjC debugging patterns.
- **PyXA Installation:** To use PyXA examples in this skill, see the installation instructions in `automating-mac-apps` skill (PyXA Installation section).
## Core Framing
Reminders works like a database: everything is accessed via specifiers (references to objects). Start by exploring the Reminders dictionary in Script Editor (switch to JavaScript view). Read properties with methods like `name()` or `id()`; write with assignments. Use `.whose` for efficient server-side filtering to minimize performance overhead. For creation, use constructors + `.push()` instead of `make` to avoid errors. Note: no native `move` command—use copy-delete instead. Priority: 1 (high), 5 (medium), 9 (low), 0 (none). Recurrence/location scripting is limited; use Shortcuts for advanced features.
## Quickstart (create + alerts)
First, ensure Reminders permissions are granted (see `automating-mac-apps` for setup).
**JXA:**
```javascript
try {
const app = Application("Reminders");
// Get list by name, or fall back to first available list
let list;
try {
list = app.lists.byName("Reminders");
list.name(); // Verify it exists
} catch (e) {
// Fall back to first available list
const lists = app.lists();
if (lists.length === 0) {
throw new Error("No reminder lists found");
}
list = lists[0];
}
const r = app.Reminder({
name: "Prepare deck",
body: "Client review",
dueDate: new Date(Date.now() + 3*86400*1000), // 3 days from now
remindMeDate: new Date(Date.now() + 2*86400*1000), // Reminder 1 day before due
priority: 1 // High priority
});
list.reminders.push(r);
console.log("Reminder created in '" + list.name() + "'");
} catch (error) {
console.error("Failed to create reminder: " + error.message);
// Common errors: Permissions denied, list not found
}
```
> **Note:** The list name varies by system. Common names include "Reminders", "Inbox", or localized versions. Using `app.lists()[0]` as a fallback ensures the script works across different configurations.
**PyXA (Recommended Modern Approach):**
```python
import PyXA
from datetime import datetime, timedelta
try:
reminders = PyXA.Reminders()
# Get Inbox list
inbox = reminders.lists().by_name("Inbox")
# Create reminder with due date and reminder alert
reminder = inbox.reminders().push({
"name": "Prepare deck",
"body": "Client review",
"due_date": datetime.now() + timedelta(days=3),
"remind_me_date": datetime.now() + timedelta(days=2),
"priority": 1 # High priority
})
print("Reminder created successfully")
except Exception as error:
print(f"Failed to create reminder: {error}")
# Common errors: Permissions denied, Inbox list not found
```
**PyObjC with Scripting Bridge:**
```python
from ScriptingBridge import SBApplication
from Foundation import NSDate
try:
reminders = SBApplication.applicationWithBundleIdentifier_("com.apple.Reminders")
# Get Inbox list
lists = reminders.lists()
inbox = None
for lst in lists:
if lst.name() == "Inbox":
inbox = lst
break
if inbox:
# Create reminder
reminder = reminders.classForScriptingClass_("reminder").alloc().init()
reminder.setName_("Prepare deck")
reminder.setBody_("Client review")
# Set due date (3 days from now)
due_date = NSDate.dateWithTimeIntervalSinceNow_(3 * 24 * 60 * 60)
reminder.setDueDate_(due_date)
# Set reminder date (2 days from now)
remind_date = NSDate.dateWithTimeIntervalSinceNow_(2 * 24 * 60 * 60)
reminder.setRemindMeDate_(remind_date)
reminder.setPriority_(1) # High priority
# Add to inbox
inbox.reminders().addObject_(reminder)
print("Reminder created successfully")
else:
print("Inbox list not found")
except Exception as error:
print(f"Failed to create reminder: {error}")
```
## Workflow (default)
1) **Discover**: Open Script Editor, view Reminders dictionary in JavaScript mode to learn available properties.
2) **Target List**: Get your list by name (e.g., `app.lists.byName('Work')`) or ID.
3) **Filter**: Use `.whose` for queries (e.g., `reminders.whose({name: {_contains: 'meeting'}})`). For dates, use `_lessThan`/`_greaterThan`.
4) **Create**: Build with `Reminder({...})` then add via `.push()` to avoid errors.
5) **Batch Operations**: Collect IDs before changes, update/delete in batches.
6) **Move**: Copy item to new list, then delete original (no native move).
7) **Advanced Features**: For recurrence/location, call Shortcuts or clone template item.
**Example: Filter overdue reminders:**
```javascript
const overdue = list.reminders.whose({dueDate: {_lessThan: new Date()}})();
```
## Validation Checklist
After implementing Reminders automation:
- [ ] Verify Reminders permissions granted
- [ ] Test list access: `app.lists().length > 0`
- [ ] Confirm reminder creation with valid dates
- [ ] Check reminder appears in Reminders UI
- [ ] Validate `.whose` queries return expected results
## Common Pitfalls
- **Permission errors**: Grant Reminders access in System Preferences > Security & Privacy.
- **-10024 errors**: Use constructor + push instead of make.
- **Invalid dates**: Validate before assignment.
- **Missing lists**: Check existence with `app.lists.byName(name)` before use.
## When Not to Use
- For cross-platform task management (use Todoist API or similar)
- When complex recurrence patterns are needed (limited JXA support; use Shortcuts)
- For non-macOS platforms
- When location-based reminders require programmatic setup (use Shortcuts)
## What to Load
Load progressively as needed:
- **Basics**: Start with `automating-reminders/references/reminders-basics.md` for specifiers and simple operations.
- **Recipes**: Add `automating-reminders/references/reminders-recipes.md` for practical create/query/batch examples.
- **Advanced**: For complex scenarios, load `automating-reminders/references/reminders-advanced.md` (priority, limits, debugging).
- **Dictionary**: Reference `automating-reminders/references/reminders-dictionary.md` for full type mappings.
- **PyXA API Reference** (complete class/method docs): `automating-reminders/references/reminders-pyxa-api-reference.md`Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.