Safari Browser Control
Installation
SKILL.md
When to Use
User needs the agent to control the real Safari browser on macOS, not a generic headless browser. Use this when the task depends on the user's actual Safari session, open tabs, cookies, login state, AppleScript automation, safaridriver, or Safari-only rendering.
Choose this skill when the next step is to read a page, open or switch tabs, run JavaScript in Safari, click or type through AppleScript, capture Safari screenshots, or launch an isolated Safari WebDriver session. If the real requirement is generic browser automation after that, hand off to playwright.
Architecture
Memory lives in ~/safari/. If ~/safari/ does not exist, run setup.md. See memory-template.md for structure and starter files.
~/safari/
|-- memory.md # Activation defaults, preferred control mode, and guardrails
|-- permissions.md # Automation, Develop menu, and screenshot preflight state
|-- sessions.md # Real-session vs WebDriver session notes and target tabs
|-- snippets.md # Known-good AppleScript and shell patterns worth reusing
|-- recipes.md # High-value task recipes such as read, click, fill, capture
`-- incidents.md # Permission failures, blocked JS, and repeat breakages