Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →pramoddutta/Vibe Check - Browser Automation
Browser automation for AI agents. Navigate pages, fill forms, click elements, take screenshots, and manage tabs — all through simple CLI commands. 2.6k+ GitHub stars.
Passed 22 of 22 test cases with the skill, and 5 of 22 without it.
and 20 more in the full report
17 fixed5 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to test responsive layout behavior at a mobile dimension of 375x812 with a retina device pixel ratio of 3. What command line invocation configures both the dimensions and pixel density?
| Checked | Without skill | With skill |
|---|---|---|
| Passes the device pixel ratio flag alongside width and height dimensions | Passed | Passed |
| Uses vibium set-viewport | Missed | Passed |
The instructions your model reads when the skill loads.
The vibium CLI automates Chrome via the command line. The browser auto-launches on first use (daemon mode keeps it running between commands).
vibium go <url> && vibium map && vibium click @e1 && vibium map
Every browser automation follows this pattern:
vibium go <url>vibium map (get element refs like @e1, @e2)vibium click @e1vibium mapBefore running any commands, resolve the vibium binary path once:
vibium directly (works if globally installed via npm install -g vibium)./clicker/bin/vibium (dev environment, in project root)./node_modules/.bin/vibium (local npm install)Run vibium --help (or the resolved path) to confirm. Use the resolved path for all subsequent commands.
Windows note: Use forward slashes in paths (e.g. ./clicker/bin/vibium.exe) and quote paths containing spaces.
Chain commands with && to run them sequentially. The chain stops on first error:
vibium go https://example.com && vibium map && vibium click @e3 && vibium diff map
When to chain: Use && for sequences that should happen back-to-back (navigate → interact → verify). Run commands separately when you need to inspect output between steps.
When NOT to chain: Don't chain commands that depend on parsing the previous output (e.g. reading map output to decide what to click). Run those separately so you can analyze the result first.
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.