Agent skill · software engineering · jeremylongshore

apple-notes-rate-limits

Handle Apple Notes automation rate limits and iCloud sync throttling.

Why this skill is useful

Adds executable scripts for managing Apple Notes automation with specific rate limits and error handling that aren't publicly documented.

What it needs

Requires jq installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Apple Notes Rate Limits Overview Apple Notes has no formal API rate limits like cloud services do. However, there are practical throughput limits imposed by three systems: the Apple Events IPC bridge (osascript to Notes.app), the iCloud sync daemon (bird/cloudd) that must process each write, and the Notes.app SQLite database that handles concurrent access. Exceeding these practical limits causes timeouts (-1712), sync lag, or data loss when writes outpace iCloud's upload buffer. This guide documents safe operation rates and provides throttling patterns. Prerequisites A tested Notes adapter that keeps note data out of command strings and logs. A bounded queue with an idempotency key or durable operation ledger for each write. An approved maintenance window and backup for bulk mutations; the rates below are conservative starting points, not a vendor guarantee. Instructions 1. Begin below the listed rates and increase only after observing successful sync on every required device. 2. Serialize writes and deletes; do not retry a timed-out mutation until a durable idempotency check determines whether it succeeded. 3. Pause the queue and escalate if timeout, sync lag, or duplicate detection crosses the service threshold. 4. Do not terminate iCloud processes to recover throughput; preserve evidence and use normal OS recovery procedures. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/apple-notes-rate-limits

View the source on GitHub

Browse the @skills marketplace