Agent skill · data analytics · jeremylongshore
apple-notes-observability
Monitor Apple Notes automation health and performance metrics.
Why this skill is useful
Adds a set of bash scripts for monitoring Apple Notes health that are not commonly found in public documentation.
What it needs
Requires jq 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 Observability Overview Apple Notes has no built-in metrics API or health endpoint. Observability must be built from the outside: polling note counts and folder states via JXA, monitoring iCloud sync daemon health, tracking osascript response latency, and watching system logs for Notes-related errors. This guide sets up a lightweight monitoring stack using bash scripts, structured JSON logs, and macOS notifications for alerting. For persistent monitoring, deploy the health check as a launchd agent that runs on a schedule. Prerequisites A job-owned, permission-restricted log directory with rotation and retention limits. A monitoring scope limited to the approved account/folder; counts are sensitive operational metadata and must not be sent to broad telemetry. A defined alert owner and a sustained-failure threshold so transient iCloud or TCC conditions do not trigger unsafe remediation. Instructions 1. Collect only health status, bounded latency, and coarse scoped counts required for the alert decision. 2. Sanitize shell output before emitting JSON; do not interpolate account names, note titles, bodies, or raw errors into notifications. 3. Alert after the agreed consecutive failure threshold and link to the incident runbook. 4. Rotate logs and review access periodically; monitoring must never restart iCloud processes or modify Notes state. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apple-notes-observability