agentleFS
krmj22krmj22/macos-mcp/skills/macos/SKILL.md

macos

Skill8 starsChanged 6 months agoMITView on GitHub

Read or change native macOS apps from the shell — Reminders, Calendar, Notes, Mail, Messages/iMessage, Contacts. Fire whenever a request names or implies one: "remind me to", "what's on my calendar", "text X", "any mail from Y", "make a note", "complete a reminder", "add an event", or resolve a phone number or email address to a contact name.

  • Installs packages

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. suitedaces/dorabot★ 247same name
    2. kingsidharth/skills★ 17same name
    3. Lukk17/agent-standards★ 1same name
    4. hebertzhu/agent-foundry★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run once per session if anything fails:

    line 20
  2. Very specific:

    Do not point the link at an npm cache path (~/.npm/_npx/...).

    line 35
  3. Very specific:

    All output is JSON: {"status":"success","result":...} or {"status":"error","message":...}, exit 1 on error.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

macOS app control

Drives the native macOS apps through three bridges:

BridgeAppsWhy this one
EventKitCLI (Swift binary)Reminders, CalendarEventKit is the only API with full read/write on both
JXA via osascriptNotes, Contacts, Mail writes, Messages sendApple Events is the only thing that triggers a write
sqlite3 direct readsMail, MessagesJXA Messages reads return nothing on Sonoma and later; JXA Mail reads time out at 60s on a real inbox

Same primitives the mcp-macos MCP server uses. This skill calls them directly, so no tool schemas sit in context until something triggers the skill.

Setup check

Run once per session if anything fails:

ls -lL ~/.local/bin/EventKitCLI   # -L follows the symlink

⚠️ Check the link TARGET, not just its presence. A dangling symlink passes command -v and then fails at exit 127. Verify with ls -lL or readlink. If the target is gone, re-vendor the binary:

cd "$(mktemp -d)" && npm i mcp-macos --no-save \
  && mkdir -p ~/.local/lib/mcp-macos/bin \
  && cp node_modules/mcp-macos/bin/EventKitCLI ~/.local/lib/mcp-macos/bin/EventKitCLI \
  && ln -sf ~/.local/lib/mcp-macos/bin/EventKitCLI ~/.local/bin/EventKitCLI

Do not point the link at an npm cache path (~/.npm/_npx/...). npm prunes it.

Permissions

BridgeSystem SettingsFailure looks like
EventKitCLI RemindersPrivacy & Security → Reminders (full access){"status":"error"} with a permission message
EventKitCLI CalendarPrivacy & Security → Calendars (full access)same
JXA Notes / Contacts / Mail / MessagesPrivacy & Security → Automation → the apposascript hangs, or "Not authorized to send Apple events"
sqlite3 Mail / MessagesPrivacy & Security → Full Disk Access on your terminalunable to open database file

Full Disk Access is granted to the terminal binary, not to sqlite3. Version manager users need the real node binary, not the shim.

Verify JXA quickly:

osascript -l JavaScript -e 'Application("Contacts").people().length'
osascript -l JavaScript -e 'Application("Notes").notes().length'

Each should return a number. A hang means the permission dialog is trying and failing to appear.

Reminders

All output is JSON: {"status":"success","result":...} or {"status":"error","message":...}, exit 1 on error.

# Read all open reminders
EventKitCLI --action read --showCompleted false

# Server-side filters: --filterList "<name>"  --search "<term>"
#   --dueWithin overdue|today|tomorrow|this-week|no-date
EventKitCLI --action read --showCompleted false --dueWithin today

# Create (--title required). Dates: "YYYY-MM-DD HH:mm:ss" is local time.
# Append Z or an offset for an explicit zone. A bare date makes it all-day.
EventKitCLI --action create --title "Buy milk" --targetList "Groceries" \
  --note "2% organic" --dueDate "2026-06-25 17:00:00"

# Update (--id required; only supplied fields change)
EventKitCLI --action update --id "<id>" --isCompleted true
EventKitCLI --action update --id "<id>" --title "New title" --dueDate "2026-06-26 09:00:00"

# Delete
EventKitCLI --action delete --id "<id>"

# Lists
EventKitCLI --action read-lists
EventKitCLI --action create-list --name "New List"
EventKitCLI --action update-list --name "Old" --newName "New"
EventKitCLI --action delete-list --name "List To Delete"

Calendar

⚠️ Always pass a bounded date range on reads. The EventKit predicate cannot span more than 4 years, and omitting the dates returns nothing useful.

EventKitCLI --action read-events \
  --startDate "2026-06-01 00:00:00" --endDate "2026-07-01 00:00:00"
# optional: --filterCalendar "Work"  --search "standup"

EventKitCLI --action read-calendars

# Create (--title, --startDate, --endDate required)
EventKitCLI --action create-event --title "Team sync" \
  --startDate "2026-06-20 10:00:00" --endDate "2026-06-20 11:00:00" \
  --targetCalendar "Work" --location "Zoom" --notes "Agenda in Notes" \
  --url "https://example.com/room"

# Recurrence: --recurrence daily|weekly|monthly|yearly
#   --recurrenceInterval N   and EITHER --recurrenceEnd "<date>" OR --recurrenceCount N
EventKitCLI --action create-event --title "Standup" \
  --startDate "2026-06-23 09:00:00" --endDate "2026-06-23 09:15:00" \
  --recurrence weekly --recurrenceInterval 1 --recurrenceCount 12

# Update (--id required; --url "" clears the URL)
EventKitCLI --action update-event --id "<id>" --location "Room 2"

# Delete removes the single occurrence, not the series
EventKitCLI --action delete-event --id "<id>"

findEventById needs the same bounded range. An unbounded lookup returns 0 events even when the event exists.

Notes, Contacts, Mail, Messages

Recipes live in the reference files. Read the one you need before writing any JXA or SQL, because both bridges have failure modes that look like success:

  • references/notes-contacts.md — Notes CRUD and folders, Contacts CRUD and search, and the phone/email to name enrichment cache.
  • references/mail-messages.md — Messages reads from chat.db, Mail reads from the Envelope Index including the Gmail label join, Mail drafts and Messages send via JXA.

Safety

  • A draft is not a send. Building a Mail draft is reversible. Sending is not. Do not send mail on a user's behalf without an explicit instruction for that message.
  • iMessage send is immediate and outward-facing. There is no draft state and no undo. Confirm the recipient and the text before calling it.
  • Deleting a note moves it to Recently Deleted; deleting a reminder or event does not. EventKit deletes are permanent.
  • Mail's outgoing message list is shared across every process on the machine. Never bulk-close or bulk-delete it. Target one message by identity.
  • Verify a write by reading it back. JXA reports success on writes that did not land, in both directions. A read-back is the only evidence.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.