// Umbrella skill for mobile device control in the kuri ecosystem. Points to kuri-ios (iOS Simulator + real-device listing) and kuri-android (native Zig adb client). Use this when the user asks about "mobile automation" generally, or hasn't specified a platform. For platform-specific work prefer the `kuri-ios` or `kuri-android` skill directly.
| name | kuri-mobile |
| description | Umbrella skill for mobile device control in the kuri ecosystem. Points to kuri-ios (iOS Simulator + real-device listing) and kuri-android (native Zig adb client). Use this when the user asks about "mobile automation" generally, or hasn't specified a platform. For platform-specific work prefer the `kuri-ios` or `kuri-android` skill directly. |
kuri-mobile is the Zig-native subproject at kuri-mobile/ that
adds mobile device control to the kuri browser-automation stack.
Inspired by mobile-device-mcp,
reimplemented in Zig with no Bun, Node, Gradle, or Xcode in the
build path.
Use the platform-specific skills for actual work:
kuri-ios — iOS Simulator (boot, openurl, launch, terminate,
screenshot, list-apps) + real-iPhone listing (usbmuxd) +
real-iPhone launch/terminate (devicectl).kuri-android — Android devices and emulators (tap, swipe,
type, press, screenshot, uitree, launch, terminate, list-apps)
via a native Zig adb wire-protocol client.cd kuri-mobile
zig build
zig build test
cp zig-out/bin/kuri-mobile ../zig-out/bin/ # so `kuri ios` / `kuri android` work
The main kuri binary forwards kuri android <cmd> and
kuri ios <cmd> to kuri-mobile (it execvps it from the same
directory or $PATH). So either invocation works:
kuri android list-devices
kuri-mobile android list-devices
We deliberately do not install an on-device driver app. Consequences you must be honest about:
run_code JavaScript sandbox.input, screencap, uiautomator dump,
monkey, am, pm.Full parity matrix vs mobile-device-mcp: see
kuri-mobile/README.md.
| User asks about… | Invoke |
|---|---|
| "iPhone", "iOS", "sim", "Safari on simulator", "iPad" | kuri-ios |
| "Android", "adb", "emulator", "Pixel", "Galaxy", "APK" | kuri-android |
| "mobile" without specifying | either — ask first, or default to this umbrella note |
| Browser automation (Chrome, CDP) | not a mobile skill — use kuri-server, kuri-agent, or kuri-browse |
Use kuri-ios to drive iOS Simulators from the CLI — list sims, boot/shutdown, navigate Safari to URLs (openurl), launch and terminate apps by bundle id, capture PNG screenshots, list installed apps, and (on the Simulator only) tap, doubletap, longpress, swipe/pan, and type via native CGEvent into the Simulator window. Real iPhones over USB are supported for listing and launch/terminate via usbmuxd + xcrun devicectl. Tap/swipe/type/uitree on real devices and uitree on the Simulator are NOT supported in v1 (require XCUITest). Multi-touch (pinch, rotate, two-finger pan) and hardware buttons (Home, Lock, Volume) are not wired yet. Trigger phrases include "screenshot the iPhone sim", "tap on iOS simulator", "doubletap iOS sim", "long press iOS sim", "swipe up on iPhone sim", "pan the iOS simulator", "type into iOS simulator", "open Safari on simulator", "launch iOS Settings", "list booted simulators".
Use kuri-android to drive Android devices and emulators from the CLI via a native Zig adb wire-protocol client. Tap, swipe (scroll), double-tap, long-press, type text, press hardware/navigation keys, take PNG screenshots, dump the UI tree as a flat element list, launch/terminate apps by package, list installed packages, and list attached devices. Talks adb directly over TCP 127.0.0.1:5037 — never shells out to the `adb` binary at runtime. Trigger phrases include "tap on android phone", "screenshot the emulator", "list connected android devices", "dump the android ui tree", "launch chrome on android".
Use kuri-server to automate Chrome via HTTP API — navigate pages, get a11y snapshots, interact with elements, capture network traffic (HAR), extract cookies, and bypass bot protection. Use when the user wants to browse websites, scrape data, fill forms, test web apps, or interact with protected sites via a headless browser. Trigger phrases include "browse to", "open the page", "get the page content", "fill the form", "capture network traffic", "get cookies", "bypass bot protection".
Use kuri-browse for quick terminal-based web browsing — fetch and read web pages as markdown, follow links, search in-page. No Chrome needed. Use when the user wants to quickly read a webpage, check documentation, or browse without launching a full browser. Trigger phrases include "read this page", "fetch the docs", "browse to", "what does this page say".
Use kuri-agent to automate Chrome — navigate pages, interact with elements via a11y refs, capture screenshots, run security audits, enumerate cookies/JWTs, probe for IDOR vulnerabilities, and make authenticated fetches. Use when the user wants to automate a browser, test a web app, scrape data, or run security trajectories against a live site.