Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/computer-control
Automates desktop GUI workflows via computer use API with screenshot capture.
Passed 22 of 22 test cases with the skill, and 11 of 22 without it.
and 16 more in the full report
11 fixed11 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When using claude-sonnet-4-5 or claude-haiku-4-5 for computer use, which specific tool version name and beta header string apply?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies the tool version string as computer_20250124 | Missed | Passed |
| Identifies the beta header string as computer-use-2025-01-24 | Missed | Passed |
The instructions your model reads when the skill loads.
Use Claude's Computer Use API to see and control desktop environments through screenshots and mouse/keyboard actions.
Why this stays opt-in. Per docs/inclusive-defaults.md (TRUE-exception category 4), Computer Use takes screenshots and synthesizes keyboard/mouse input: cross-process side effects that must always be explicitly invoked, never default-on.
The computer use system has three layers:
phantom.display) - executes OS-level
actions via xdotool/scrot on the real or virtual displayphantom.loop) - manages the conversation
cycle between Claude API and the display toolkitphantom.cli) - command-line interface for running
tasks or checking environment readinessUser Task
|
test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.