Skip to content
cccskills
FreePublished on GitHub

apple-notes-hello-world

Use this skill to learn basic Apple Notes automation on macOS with JXA or AppleScript through `osascript`. The examples show how to create, list, read, search, organize, and delete notes from scripts, including a test-only read/write check.

OriginalShow the original description

Create, read, and list Apple Notes using JXA and AppleScript. Use when learning Notes automation, creating your first automated note, or testing read/write access to Apple Notes from scripts. Trigger: "apple notes hello world", "create apple note", "read apple notes", "apple notes example", "osascript notes".

Run score Not tested

See how to install

Good for

  • Creating a first automated note in a test folder
  • Listing note titles and creation dates
  • Reading or searching notes by title
  • Testing script access to Notes.app

Files included (1)

  • SKILL.md5.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Apple Notes Hello World

Overview

Create, read, search, and delete Apple Notes using JXA (JavaScript for Automation) via osascript. All examples work from the command line on macOS.

Prerequisites

  • Completed apple-notes-install-auth (permissions granted)
  • macOS with Notes.app

Instructions

Step 1: Create a Note

# JXA: Create a note in the default folder
osascript -l JavaScript -e '
  const Notes = Application("Notes");
  const defaultFolder = Notes.defaultAccount.folders[0];
  const newNote = Notes.Note({
    name: "Hello from Automation",
    body: "<h1>Hello World</h1><p>This note was created via JXA at " + new Date().toISOString() + "</p>"
  });
  defaultFolder.notes.push(newNote);
  newNote.id();
'

# AppleScript equivalent:
osascript -e '
  tell application "Notes"
    tell account "iCloud"
      make new note at folder "Notes" with properties {name:"Hello AppleScript", body:"<p>Created via AppleScript</p>"}
    end tell
  end tell
'

Step 2: List All Notes

# List notes with title and creation date
osascript -l JavaScript -e '
  const Notes = Application("Notes");
  const notes = Notes.defaultAccount.notes();
  notes.slice(0, 10).map(n =>
    `${n.name()} | Created: ${n.creationDate().toISOString().split("T")[0]}`
  ).join("\n");
'

Step 3: Read a Note's Content

# Read note body (returns HTML)
osascript -l JavaScript -e '
  const Notes = Application("Notes");
  const notes = Notes.defaultAccount.notes();
  const target = notes.find(n => n.name() === "Hello from Automation");
  if (target) {
    `Title: ${target.name()}\nBody: ${target.body()}\nModified: ${target.modificationDate()}`;
  } else {
    "Note not found";
  }
'

Step 4: Search Notes

# Search by keyword in note name
osascript -l JavaScript -e '
  const Notes = Application("Notes");
  const query = "Hello";
  const results = Notes.defaultAccount.notes().filter(n =>
    n.name().toLowerCase().includes(query.toLowerCase())
  );
  results.map(n => n.name()).join("\n") || "No results";
'

Step 5: Create Note in Specific Folder

# Create a folder and add a note to it
osascript -l JavaScript -e '
  const Notes = Application("Notes");
  const account = Notes.defaultAccount;

  // Create folder if it does not exist
  let folder = account.folders().find(f => f.name() === "Automation");
  if (!folder) {
    folder = Notes.Folder({ name: "Automation" });
    account.folders.push(folder);
  }

  // Add note to folder
  const note = Notes.Note({
    name: "Organized Note",
    body: "<p>This note lives in the Automation folder.</p>"
  });
  folder.notes.push(note);
  `Created in folder: ${folder.name()}`;
'

Step 6: Delete a Note

# Delete by name (moves to Recently Deleted)
osascript -l JavaScript -e '
  const Notes = Application("Notes");
  const notes = Notes.defaultAccount.notes();
  const target = notes.find(n => n.name() === "Hello from Automation");
  if (target) {
    Notes.delete(target);
    "Note deleted";
  } else {
    "Note not found";
  }
'

Note Properties

PropertyTypeWritableDescription
namestringYesNote title (first line)
bodystring (HTML)YesFull note content as HTML
idstringNoUnique identifier
creationDateDateNoWhen note was created
modificationDateDateNoLast modification
containerFolderNoParent folder

Output

  • Created a note via JXA and AppleScript
  • Listed, searched, and read note content
  • Organized note into a folder
  • Deleted a note

Examples

Create one synthetic note in a pre-created, test-only local folder, read only that note back by its returned identifier, and remove it after verifying the exercise. Do not list all notes, search a live account, or create folders implicitly as part of a permission smoke test.

Error Handling

ErrorCauseSolution
Notes got an errorNotes.app not runningAdd Notes.activate() first
Empty bodyNote has no text contentCheck note is not just an image
Can't make folderFolder already existsCheck before creating
Slow responseiCloud sync in progressWait for sync; use local account

Resources

Next Steps

Proceed to apple-notes-local-dev-loop for development workflow setup.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

See all skills by jeremylongshore

Report a problem with this skill