Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vellum-ai/app-control
Drive a specific named macOS app via raw input bypassing the Accessibility tree
Passed 15 of 20 test cases with the skill, and 5 of 20 without it.
and 9 more in the full report
10 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
In a custom canvas viewer (`com.graphics.viewer`), I captured a screen observation 30 seconds ago. Before clicking on a button at coordinates x=150, y=200, the user resized and moved the application window. Can I safely pass those previous x,y coordinates directly into the click tool?
| Checked | Without skill | With skill |
|---|---|---|
| Mandates re-observing the screen state before performing coordinate-based mouse actions after window movement. | Passed | Passed |
| Explains that click and drag coordinates in app-control are relative to the application window position. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill exposes the app_control_* proxy tools for driving a single
named macOS application via raw input — keyboard, mouse, screenshot — that
bypasses the system Accessibility tree. Use it only when explicitly directed
to a specific app where the AX tree is unhelpful (emulators, games, OpenGL
canvases, custom-rendered Electron apps). For general macOS UI navigation
prefer the computer-use skill.
Tools in this skill are proxy tools — execution is forwarded to the connected macOS client, never handled locally by the assistant.
Take 2-3 actions per turn, then yield with a short narration so the user can interject. Do not chain long sequences without surfacing what you are doing.
Call app_control_observe before your first input action whenever the screen
state matters (e.g. you need to know what is on screen, where a UI element is,
or whether the app is even running). Re-observe after actions that may have
moved the window or changed visibility.
observe waits a short settle delay (default ~200ms) before capturing so the
target app and the WindowServer can flush pending input and composite a fresh
frame. If the captured screenshot looks one input behind the latest state
(common with emulators or other slow-feedback apps), pass a larger
settle_ms. For static UIs where you just want a quick snapshot, pass
settle_ms: 0 to skip the wait.
app_control_sequence over multiple back-to-back app_control_press
calls when sending an ordered batch of presses (e.g. menu navigation,
repeated movement). Sequence runs in a single round-trip — the target app is
activated once at the start and the keys are sent serially without any
window for keyboard focus to drift to another app between presses. Each step
may carry its own duration_ms (hold) and gap_ms (pause after).app_control_combo over rapid sequential app_control_press for
simultaneous inputs (e.g. cmd+shift+4). combo holds every key at once;
sequential presses interleave key-down and key-up events.test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.