Agent skill · operations · jeremylongshore
apple-notes-incident-runbook
Incident response runbook for Apple Notes automation failures.
Why this skill is useful
Provides specific incident response scripts and procedures for Apple Notes automation failures that the AI wouldn't reliably generate on its own.
What it needs
Requires osascript, sqlite3 installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Apple Notes Incident Runbook Overview This runbook covers the most common Apple Notes automation failures and their resolution procedures. Unlike cloud SaaS incidents that involve API endpoints and status pages, Apple Notes incidents are local to the macOS machine: app crashes, TCC permission revocations, iCloud sync failures, and database corruption. Each incident section follows a detect-diagnose-fix-verify structure. Keep this runbook accessible on any machine running Notes automation. Prerequisites A named incident owner, an approved maintenance window for recovery actions, and a verified backup status. A redacted diagnostic location with restricted access; notes, account names, and raw unified logs can contain sensitive data. A documented escalation route to Apple or device management for sync, TCC, and storage failures. Instructions 1. Stop automated writes first and preserve the last successful cursor or operation ledger. 2. Collect minimal, redacted diagnostics and classify the incident before restarting applications or services. 3. Use supported UI, MDM, or vendor recovery paths for permissions, iCloud, and storage; do not modify TCC or Notes databases directly. 4. Validate recovery with a scoped read-only check, reconcile pending mutations, and obtain owner approval before resuming writes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apple-notes-incident-runbook