MobAI-App

Control Android and iOS mobile devices through the MobAI HTTP API. Use this skill when the user asks to interact with mobile devices, take screenshots, tap elements, type text, swipe, launch apps, or automate mobile tasks.

(PREFERRED) Execute native UI automation tasks on mobile devices using DSL batch execution. Use this skill FIRST when user asks to test apps, tap elements, verify screens, automate, or interact with devices. Works with native apps like Settings, Mail, Instagram AND browser chrome UI (address bar, tabs, nav buttons) using accessibility tree and element predicates.

Execute web automation tasks on mobile browsers and WebViews using DSL batch execution. Use when you need CSS selectors, JavaScript execution, or DOM manipulation. Try native-runner first for simple taps/types. NOT for browser chrome UI (address bar, tabs, nav buttons are native).

Direct iOS/Android device control via MobAI's DSL. Use when the user wants to automate, test, or interact with a real phone, simulator, or emulator. Requires MobAI to be running locally.

iOS Settings (com.apple.Preferences). Apple's first-party device-config app - open About, set language/region, toggle airplane mode, set dark mode, etc.

Use when the user asks to record / produce / export a screencast or demo video of a macOS desktop or web app - for launch, marketing, social posts, landing pages, internal walkthroughs. Triggers on "record a screencast", "screen recording", "desktop app demo", "web app demo", "record this Mac app", "make a screencast", "marketing video for the app", "record Chrome / Safari". Enforces explore → script → dry-run → record → export. macOS only. For mobile demos use the sibling `mobile-recorder-skill`.