Macos Automation

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

assistant/CLAUDE.md

assistant/src/approvals/CLAUDE.md

assistant/src/notifications/CLAUDE.md

assistant/src/runtime/CLAUDE.md

gateway/CLAUDE.md

Audit 0.4.1 · source sha 19bc86343b63 · 14 Oct 2026Report an issue or request a re-scan

• Publishervellum-ai GitHub organizationOwner of the repository this skill is read from
• Source foldervellum-ai/vellum-assistant/skills/macos-automationThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict19bc86343b63A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Automate native macOS apps and system interactions via osascript (AppleScript)

---
name: macos-automation
description: Automate native macOS apps and system interactions via osascript (AppleScript)
compatibility: "Designed for Vellum personal assistants"
metadata:
  icon: assets/icon.svg
  emoji: "🍎"
  vellum:
    category: "system"
    display-name: "macOS Automation"
    platforms:
      - macos
    activation-hints:
      - "Interacting with native macOS apps (Messages, Contacts, Calendar, Mail, Reminders, Music, Finder, etc.) via osascript"
    avoid-when:
      - "Tasks that can be done entirely in the sandbox or via CLI tools"
---

Use this skill to interact with native macOS apps and system-level features via `osascript` (AppleScript) through `host_bash`. Always prefer osascript over browser automation or computer-use for anything involving a native macOS app.

## Supported Apps

**Communication:** Messages, Mail, Microsoft Outlook, FaceTime
**Contacts & Calendar:** Contacts, Calendar, Reminders
**Notes & Writing:** Notes, TextEdit, Pages, BBEdit, CotEditor
**Files:** Finder, Path Finder
**Browsers:** Safari, Google Chrome
**Music & Media:** Music (iTunes), Spotify, VLC, Podcasts, TV
**Productivity:** OmniFocus, Things 3, OmniOutliner, OmniPlan, OmniGraffle
**Office:** Microsoft Word, Microsoft Excel, Numbers, Keynote
**Developer tools:** Xcode, Terminal, iTerm2, Script Editor
**System:** System Events (UI scripting for any app), System Settings
**Automation:** Keyboard Maestro, Alfred, Automator
**Creative:** Adobe Photoshop, Final Cut Pro

For any unlisted app, check scriptability first:

```bash
osascript -e 'tell application "AppName" to get name'
```

## Examples

```bash
# Send an iMessage
osascript -e 'tell application "Messages" to send "Hello!" to buddy "[email protected]"'

# Look up a contact
osascript -e 'tell application "Contacts" to get {name, phones} of every person whose name contains "Marina"'

# Read upcoming calendar events
osascript -e 'tell application "Calendar" to get summary of every event of calendar "Home" whose start date > (current date)'

# Create a reminder
osascript -e 'tell application "Reminders" to make new reminder with properties {name:"Buy milk", due date:((current date) + 1 * hours)}'

# Send an email
osascript -e 'tell application "Mail" to send (make new outgoing message with properties {subject:"Hi", content:"Hello", visible:true})'

# Create a note
osascript -e 'tell application "Notes" to make new note at folder "Notes" with properties {body:"My note"}'

# Open a URL in Safari
osascript -e 'tell application "Safari" to open location "https://example.com"'

# Play/pause Music
osascript -e 'tell application "Music" to playpause'

# Display a system notification
osascript -e 'display notification "Done!" with title "Vellum"'
```

## Tips

- For multi-line scripts, write them to a `.applescript` file and run with `osascript path/to/script.applescript`
- Use `System Events` for UI scripting apps that don't have their own AppleScript dictionary
- AppleScript permissions are gated by macOS TCC - if a command fails with a permission error, use `request_system_permission` to prompt the user

Excerpt, first 3,110 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/vellum-ai/vellum-assistant
git -C vellum-assistant checkout 19bc86343b63

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 19bc86343b63

Questions about Macos Automation

• github.com/vellum-ai/vellum-assistant/tree/main/skills/macos-aut — the audited source at commit 19bc86343b63 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology