skills/apple-bridges/SKILL.md
Use this skill whenever the user asks about Apple apps — Reminders, Calendar, Contacts, Notes, Mail, or tmux sessions. This includes creating/completing reminders, checking/adding calendar events, looking up contacts, reading/writing notes, sending/reading email, and capturing tmux session content. Also use this skill when the user mentions tasks, todos, scheduling, birthdays, free time slots, or end-of-day summaries. The bridges are CLI tools installed at ~/.claude/ that give Claude Code native access to these Apple apps on macOS.
npx skillsauth add more-io/claude-apple-bridges apple-bridgesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Swift CLI tools at ~/.claude/ that give Claude Code native access to Apple apps on macOS.
| Bridge | Binary | Purpose |
|--------|--------|---------|
| reminders-bridge | ~/.claude/reminders-bridge | Manage Apple Reminders — lists, items, due dates, search |
| calendar-bridge | ~/.claude/calendar-bridge | Read/write Apple Calendar — events, free slots, scheduling |
| contacts-bridge | ~/.claude/contacts-bridge | Search/manage Apple Contacts — lookup, birthdays |
| notes-bridge | ~/.claude/notes-bridge | Read/write Apple Notes — create, search, append |
| mail-bridge | ~/.claude/mail-bridge | Read/send Apple Mail — inbox, unread, compose |
| tmux-bridge | ~/.claude/tmux-bridge | Read/write tmux sessions — panes, snapshots, send keystrokes |
Read the detail file for the bridge you need — each contains full command syntax, all parameters, and usage examples.
All bridges follow the same pattern:
~/.claude/<bridge-name> <command> [arguments...]
Arguments with spaces must be quoted:
~/.claude/reminders-bridge add "Shopping List" "Buy milk" "From the organic store"
~/.claude/calendar-bridge add "Work" "Team Meeting" "2026-03-01 10:00" "2026-03-01 11:00"
Delete commands use a dry-run by default pattern — they show what would be deleted without the --force flag:
# Dry run (safe preview)
~/.claude/reminders-bridge delete "Work" "Old task"
# Actually delete
~/.claude/reminders-bridge delete "Work" "Old task" --force
This applies to: reminders-bridge delete, calendar-bridge delete, contacts-bridge delete, notes-bridge delete, mail-bridge delete.
Each bridge requires macOS permission on first use:
| Bridge | Permission | Settings Path | |--------|-----------|---------------| | reminders-bridge | Reminders | Privacy & Security > Reminders | | calendar-bridge | Calendars | Privacy & Security > Calendars | | contacts-bridge | Contacts | Privacy & Security > Contacts | | notes-bridge | Automation (Notes.app) | Privacy & Security > Automation | | mail-bridge | Automation (Mail.app) | Privacy & Security > Automation | | tmux-bridge | None (uses tmux CLI) | — |
Add to .claude/settings.local.json:
{
"permissions": {
"allow": [
"Bash(~/.claude/reminders-bridge:*)",
"Bash(~/.claude/calendar-bridge:*)",
"Bash(~/.claude/contacts-bridge:*)",
"Bash(~/.claude/notes-bridge:*)",
"Bash(~/.claude/mail-bridge:*)",
"Bash(~/.claude/tmux-bridge:*)"
]
}
}
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.