Agent skill · software engineering · jeremylongshore
apple-notes-debug-bundle
Collect Apple Notes automation debug evidence for troubleshooting.
Why this skill is useful
Adds an executable script that collects detailed diagnostic information for troubleshooting Apple Notes automation, which is not commonly available in public documentation.
What it needs
Requires osascript, tar 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 Debug Bundle Overview This debug bundle collects diagnostic information from Apple Notes automation integrations for troubleshooting AppleScript and JXA (JavaScript for Automation) workflows. It captures macOS version compatibility, Notes.app account configuration, folder and note counts, TCC (Transparency, Consent, and Control) permission status, and Shortcuts automation entitlements. The resulting tarball helps diagnose permission denials, sandbox restrictions, iCloud sync failures, and scripting bridge errors that commonly block Notes automation. Prerequisites macOS 12+ with Notes.app configured osascript, tar available (built into macOS) Terminal granted Automation permission for Notes.app in System Preferences > Privacy & Security Instructions 1. Obtain incident-owner approval and choose a private, access-controlled destination before collection. 2. Collect platform version, job configuration, and redacted error classifications first; include account or folder metadata only when essential to diagnosis. 3. Exclude note titles, bodies, attachment names, TCC database rows, Keychain values, and full home-directory listings. 4. Encrypt the bundle in transit, share it only with the incident responders, and delete it at the documented retention deadline. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/apple-notes-debug-bundle