Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dry-software/nib
You are performing desktop automation using `nib` (nut.js Instrumentation Bundle).
Passed 11 of 17 test cases with the skill, and 2 of 17 without it.
and 9 more in the full report
12 fixed2 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What CLI command scrolls down 5 units on text area element `@txa:LogView` inside window 'Log Viewer'?
| Checked | Without skill | With skill |
|---|---|---|
| Uses nib scroll-element @txa:LogView down 5 --window "Log Viewer" | Missed | Passed |
The instructions your model reads when the skill loads.
You are performing desktop automation using nib (nut.js Instrumentation Bundle).
Execute the following task: $ARGUMENTS
Run commands via Bash: nib <command> [options]
All commands return JSON to stdout. Always parse and check the ok field:
{"ok":true, "command":"...", "data":{...}}
{"ok":false,"command":"...", "error":{"code":"...","message":"...","suggestion":"..."}}
If a command fails, read the error message and suggestion carefully before retrying.
Before starting, run nib status and check data.permissions. On macOS, accessibility and screenRecording must both be true — otherwise a11y and window-title commands fail with PERMISSION_DENIED. If a permission is missing, run nib request-permissions once to trigger the system prompt, tell the user to approve it (and restart the host app), and wait for their confirmation. Do not retry a failed command or re-run request-permissions in a loop — granting requires user action, and macOS shows the prompt only once per app.
Always prefer accessibility-based element interaction over coordinate-based mouse clicks. Element refs are robust against layout changes and resolution differences.
# 1. Discover and focus the target window
nib list-windows
nib focus-window "App Name"
# 2. Take an accessibility snapshot (interactive-only is faster)
nib snapshot --window "App Name" -i
# 3. Read the refs from the snapshot output, then interact
nib click-element @btn:Save --window "App Name"
test cases passed, vs 2 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.