Chrome
Google Chrome heuristics for background-computer-use. Use when the user asks you to navigate, scroll, click links, fill forms, or otherwise drive Chrome without stealing focus. Also applies to Chromium-family browsers (Brave, Edge, Arc) that share the same AppleScript JavaScript execution primitive.
Install
$ agentstack add skill-panchangam18-background-computer-use-chrome ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-panchangam18-background-computer-use-chrome) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Driving Chrome with background computer use
Chrome is Chromium-based and cooperates well with background automation once the server enables AXManualAccessibility (which happens automatically on the first get_app_state).
- Call
get_app_state app="Google Chrome"before interacting. The webpage
DOM is exposed as accessibility nodes under a single HTML content element.
- URL navigation: set the
Address and search bartext field.
set_value app="Google Chrome" element_index= value="https://…" works and submits by default.
- Clicks on in-page links and buttons: use
click(element_index=...).
Chrome honors AXPress on Chromium AX nodes even when the window isn't key, so clicks don't steal focus.
- Typing into form fields:
set_valueauto-falls-back to a typing
path when the AX write is rejected (which is typical for Chromium controls). Focus stays with whichever app you had foremost.
- Scrolling: `scroll app="Google Chrome" element_index=
direction="down" works via AppleScript execute ... javascript. It finds the nearest scrollable ancestor at the viewport center (so it picks the right sub-scroller in app-style pages like Gmail, LinkedIn, or Notion, not just window`).
Known limitation:
scrollfor Chrome always scrolls a window-level or sub-scroller
picked by the "viewport-center ancestor" heuristic. If you need to scroll a specific sub-region that isn't at the viewport center, click into it first to re-center the heuristic, or use press_key key="PageDown" with the understanding that it will focus Chrome.
Detailed notes live in server/app-hints/Chrome.md; they are injected as ` on every getappstate` call for Chrome.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Panchangam18
- Source: Panchangam18/background-computer-use
- License: MIT
- Homepage: https://github.com/Panchangam18/background-computer-use
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.