macOS AppleScript Fallback (Reminders / Notes / Calendar / iMessage)

Reliable macOS AppleScript fallback for creating Apple Reminders, Apple Notes, Apple Calendar events, and sending iMessage when direct tool/plugin routes are...

Security Scan

The skill's scripts and instructions are consistent with its stated purpose (local macOS AppleScript fallbacks) and do not request unrelated credentials or network access; the main risk is that using it requires granting macOS Automation (and optionally Full Disk Access) to the host which grants local control of the target apps.

Purpose & Capability

Name/description match the provided artifacts: the skill bundles four small shell wrappers that call /usr/bin/osascript to create reminders, notes, calendar events, and send iMessage. There are no unrelated binaries, no external service credentials, and no surprising capabilities requested.

Instruction Scope

SKILL.md instructs the agent to always run the bundled scripts and to guide the user through minimal follow-ups; scripts only operate via AppleScript against local apps. The troubleshooting doc correctly points out the need to approve macOS Automation prompts. It also suggests granting Full Disk Access 'if your environment requires it' — Full Disk Access is not necessary for these actions in typical setups and is a broader permission than strictly required; treat that as an optional/advanced diagnostic step, not a default.

Install Mechanism

No install spec — instruction-only with bundled scripts. Scripts are small, present in the repo, and executed locally. No downloads, no package manager installs, and no code is fetched from external URLs.

Credentials

Skill requests no environment variables, no credentials, and no config paths. The only privilege implied is macOS Automation permission for the terminal/host app to control Reminders/Notes/Calendar/Messages, which is expected and proportional to the stated functionality.

Persistence & Privilege

always:false and no mechanisms to modify other skills or system-wide agent settings. The skill does not request persistent presence or elevated platform privileges beyond the standard macOS Automation permissions the scripts need to run.

Assessment

This skill appears to do exactly what it claims: run local AppleScript via osascript to create Reminders, Notes, Calendar events, and send iMessage. Before installing/using it: (1) review the small shell scripts yourself (they are present in the package and only call osascript); (2) be prepared to grant macOS Automation permission to the terminal/host app so these scripts can control Reminders/Notes/Calendar/Messages — that permission allows the host to automate those apps, so only grant it in a trusted environment; (3) ignore the troubleshooting suggestion to grant Full Disk Access unless you understand why your environment requires it (it's broader than needed for the listed tasks); (4) test on safe data first (e.g., create a dummy note/reminder) to confirm behavior; (5) do not expect any network exfiltration from these scripts — they operate locally and do not contact remote endpoints.

macOS AppleScript Fallback

Use local shell + AppleScript for 4 tasks:

1. Create reminder (Reminders)
2. Create note (Notes)
3. Create calendar event (Calendar)
4. Send iMessage (Messages)

Prefer bundled scripts in scripts/ over ad-hoc inline AppleScript for consistency and compatibility.

Quick Start

Run these scripts directly:

# reminder
./scripts/create_reminder.sh "今晚8点吃晚饭" "2026-03-22 20:00:00"

# note (HTML body required)
./scripts/create_note.sh "<h1>武汉三日游</h1><p>Day1 黄鹤楼...</p>" "iCloud"

# calendar
./scripts/create_calendar_event.sh "跑步" "个人" "2026-03-23 08:00:00" "2026-03-23 08:30:00"

# iMessage
./scripts/send_imessage.sh "[e-mail]" "武汉下周末天气：..."

Workflow

Step 1: Clarify user intent + required fields

• Reminder: title, optional datetime
• Note: title/body content (render as HTML), optional account name
• Calendar: title, calendar name, start datetime, end datetime
• iMessage: recipient (phone or Apple ID), message text

If missing required fields, ask one concise follow-up question.

Step 2: Execute script (not plugin)

Always call the corresponding script in scripts/.

Why:

• avoids low-version parser differences
• centralizes fallback logic
• easier to debug and publish

Step 3: Confirm result to user

• If script returns an object/id or sent, report success.
• If no output but exit code is 0, still report success and suggest user verify in app UI.

Step 4: On failure, diagnose quickly

Use checks from references/troubleshooting.md.

Most frequent root causes:

• macOS Automation permission prompt not approved
• locale-dependent date parsing format
• Messages iMessage service/account not initialized
• target calendar/account name mismatch

Compatibility Rules (important)

1. Avoid locale-fragile date strings where possible.
2. Messages: resolve service by service type = iMessage, not by hard-coded service name.
3. Calendar: if named calendar doesn’t exist, fallback to first calendar.
4. Notes: if account iCloud is missing, fallback to default account.
5. Notes body uses HTML (<h1>, <p>) for stable rendering.

Output style to user

Keep concise and concrete:

• what was created/sent
• key details (time/target)
• returned ID (if any)
• one-line next step if verification needed

Bundled Resources

scripts/

• create_reminder.sh
  • args: <title> ["YYYY-MM-DD HH:MM:SS"]
• create_note.sh
  • args: <html-body> [account-name]
• create_calendar_event.sh
  • args: <title> <calendar-name> <start> <end>
• send_imessage.sh
  • args: <buddy(phone/appleid)> <message>

references/

• troubleshooting.md
  • permission/automation prompts
  • date parsing and locale issues
  • Messages service/account init
  • calendar/account fallback checks
  • diagnostic commands