Apple Notes

Problem

Engineers may need to read, create, edit, delete, search, or organize Apple Notes without leaving a terminal or IDE. This skill lets a model or script use osascript to issue Apple Events directly, treating Notes as an Apple-native note store. Content can be HTML-rich, including headings, lists, code blocks, links, and tables, and it can sync through iCloud across iPhone, iPad, and Mac.

How It Works

The skill treats note operations as verifiable AppleScript steps: check existing notes or folders first, then write with operations such as set body, then verify the result. After create, edit, delete, or move operations, it should confirm the note list or read plaintext to check the change. Longer payloads can be passed with a heredoc to reduce quoting and shell-escaping problems. For edits, prefer replacing the whole body because Notes rewrites internal HTML and local find-and-replace is fragile.

Boundaries

Use it for Apple Notes, notes, meeting records, ideas, and technical notes. Do not use it for Apple Reminders, direct Markdown file editing, or third-party systems such as Notion or Obsidian. First use requires macOS Notes permission. Since get body returns Notes-internal HTML, get plaintext is usually a safer way to verify visible text.