Install
$ agentstack add skill-appium-skills-setup-chromium ✓ 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.
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
Chromium Setup Workflow
Chromium setup routing and handoffs
Prepare only the Appium Chromium route for Chrome, Chromium, or Edge desktop browsers. Use driver-specific official guidance for an existing runtime failure after setup passes.
Required inputs
Confirm the browser and executable when non-default, global appium mode or explicitly requested local npx appium mode, host OS, permissions, and whether a session-time browser-driver download is authorized.
Workflow outline
- Load the global command profile by default or the local profile only when
explicitly requested.
- Load the Chromium profile, shared Appium setup basics, browser prerequisites,
and Chromium decision, driver-validation, and smoke references.
- Run
node tools/appium/setup/scripts/check-chromium-env.mjs; pass
--appium-mode local only for local mode. Use top-level summary.requiredOk as the read-only gate.
- Apply required fixes in technical dependency order and rerun the affected
check.
- Run
/statusand
node tools/appium/setup/scripts/smoke-chromium-session.mjs. Load the matching example only when it clarifies execution.
Chromium setup safety and approval constraints
- Ask before privileged package-manager commands, browser installation, or a
session-time browser-driver download.
- Preserve the selected command mode and existing working browser and driver
installations.
Completion criteria
- Appium succeeds in the selected command mode with major version
>= 3. - The installed driver list includes
chromium. - At least one supported Chromium browser is available.
- Doctor reports
0 required fixes neededwhen supported; otherwise the
install, list, browser, and smoke gates pass.
/statussucceeds, logs listchromium, and the minimal browser session
helper reports top-level summary.requiredOk: true.
Evidence boundary
Report Appium and driver versions, browser and executable evidence, helper and doctor summaries, /status, server driver evidence, minimal session result, and cleanup.
Self-Improvement Prompt
Before the final response, report any missing, ambiguous, outdated, or retry-causing Chromium setup instruction with its asset path and proposed wording. Leave unrelated assets unchanged.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: appium
- Source: appium/skills
- License: Apache-2.0
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.