← ClaudeAtlas

osaurus-macos-uselisted

Control macOS via accessibility APIs. Use when the user asks to interact with native Mac apps, automate UI tasks, browse the web in Safari, fill forms, navigate menus, or perform any on-screen action.
osaurus-ai/osaurus-macos-use · ★ 18 · Web & Frontend · score 62
Install: claude install-skill osaurus-ai/osaurus-macos-use
# Osaurus macOS Use Automate macOS through accessibility APIs. This plugin gives you direct control over any application's UI — click buttons, type text, fill forms, navigate menus, browse the web in Safari, and more. ## Core Workflow Every interaction follows the **Open-Observe-Act** pattern: 1. **Open the app** — `open_application` to launch/activate, returns a `pid`. 2. **Observe the UI** — ALWAYS call `get_ui_elements` with the `pid` before doing anything else. This confirms the app is ready and gives you element IDs. **Never skip this step. Never send keyboard or mouse actions before observing.** 3. **Act** — use element IDs to `click_element`, `type_text`, `set_value`, `press_key`, etc. 4. **Re-observe when the UI changes** — after navigation, dialogs, tab switches, or form submissions. Do NOT re-observe after actions that don't change the visible UI (typing, toggling, pressing shortcuts). This decoupled approach keeps token usage low. A typical 5-step interaction costs ~3K tokens vs ~150K if you re-observed after every action. ## When to Re-Observe Call `get_ui_elements` again when: - You clicked a button/link that opens a new view, dialog, page, or menu - You switched tabs or windows - You submitted a form and the UI refreshed - An element ID returns "Element not found" Do NOT re-observe when: - You just typed text into a field (the field still has focus) - You just pressed a keyboard shortcut (e.g., Cmd+S to save) - You clicked a toggle, checkbox, or other co