bluelovers/browser-automation SkillScore 95 Maintained Reliable, composable browser automation using minimal OpenCode Browser primitives.
by bluelovers
Use this skill Links this skill to your agents and keeps it current with the author’s updates.
Automatic
◆ QA & Test Engineering pack
$ decimalai skills pull bluelovers-browser-automationCopy
Copy link Copy README badge Copy SKILL.md Get this skill — curl · raw file $ curl -fsSL https://app.decimal.ai/s/bluelovers-browser-automation/SKILL.mdCopy
how this skill behaves on real traffic · last 30 days
No production data for this skill yet — usage numbers appear here once agents start running it.
Anonymized aggregate across every org using this skill — proof from real production use, not a demo. Sign in and install to see your own agents here →
Does this skill help? · Benchmark: with vs. without sign in to run this on your agents 22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 7d ago
Yes — +73% lift -30% tokens 0% turns 95% of whole cases pass with skill (21/22)
Showing 5 of 22 cases See all cases & grading →
SkillSafety ✓ 3 of 3 passed ✓ Code scan 15 of 15 checks clean
0 critical · 0 warning · 0 info — scanner v4 — 8/1/2026
live_secret remote_code_execution reverse_shell data_exfiltration ssrf_metadata agent_snooping anti_refusal destructive_commands obfuscated_unicode unicode_homoglyph opaque_blob suspicious_url tool_overreach trigger_abuse prompt_injection_phrasing
✓ Intent Safe
LLM judge · does the skill do what it claims
✓ Content Clean
LLM judge · policy & harmful-content review
Source Imported bluelovers / ai-agents-profile
skills/browser-automation/SKILL.md
View on GitHub ↗ License MITImported 8/1/2026Version v1
Contents Benchmark Live Traces Versions (1) Ratings (0)
What I do Provide a safe, composable workflow for browsing tasks Use browser_query list and index selection to click reliably Confirm state changes after each action Support CLI-first debugging with opencode-browser tool commands Best-practice workflow Inspect tabs with browser_get_tabs Open new tabs with browser_open_tab when needed Navigate with browser_navigate if needed Wait for UI using browser_query with timeoutMs Discover candidates using browser_query with mode=list Click, type, or select using index Confirm using browser_query or browser_snapshot CLI-first debugging List all available tools: npx @different-ai/opencode-browser tools Run one tool directly: npx @different-ai/opencode-browser tool browser_status Pass JSON args: npx @different-ai/opencode-browser tool browser_query --args '{"mode":"page_text"}' Run smoke test: npx @different-ai/opencode-browser self-test After update, reload the unpacked extension in chrome://extensions This path is useful for reproducing selector/scroll issues quickly before running a full OpenCode session.
Selecting options Use browser_select for native <select> elements Prefer value or label; use optionIndex when needed Example: browser_select({ selector: "select", value: "plugin" }) Query modes text: read visible text from a matched elementvalue: read input valueslist: list many matches with text/metadataexists: check presence and countpage_text: extract visible page textOpening tabs Use browser_open_tab to create a new tab, optionally with url and active Example: browser_open_tab({ url: "https://example.com", active: false }) Troubleshooting If a selector fails, run browser_query with mode=page_text to confirm the content exists Use mode=list on broad selectors (button, a, *[role="button"], *[role="listitem"]) and choose by index For inbox/chat panes, try text selectors first (text:Subject line) then verify selection with browser_query For scrollable containers, pass both selector and x/y to browser_scroll and then verify scrollTop Confirm results after each action Want to see if bluelovers/browser-automation would activate on your phrasing? Try it before you install — no LLM call, no signup. Try this skill →