Gecko Setup Workflow
Routing
Prepare only the Appium Gecko route for Firefox desktop browsers. Use
driver-specific official guidance for an existing runtime failure after setup
passes.
Required inputs
Confirm the Firefox channel or executable when non-default, global appium
mode or explicitly requested local npx appium mode, host OS, and permissions
for browser or package-manager changes.
Workflow
- Load the global command profile by default or the local profile only when
explicitly requested.
- Load the Gecko profile, shared Appium setup basics, Firefox prerequisites,
and Gecko decision, driver-validation, and smoke references.
- Run
node tools/appium/setup/scripts/check-gecko-env.mjs --format summary --report auto; add
--appium-mode local only for explicitly requested local mode. Require
top-level summary.requiredOk: true.
Apply required fixes in technical dependency order and rerun affected checks.
If the gate remains unresolved, report blocked with evidence and the next
action. Load the matching example only when needed.
- Verify
appium driver doctor gecko reports 0 required fixes needed, or
record not-supported and require the install, list, Firefox, and smoke
gates instead. Use npx --no-install appium ... for the direct check in
local mode.
- Run
node tools/appium/setup/scripts/smoke-appium-server.mjs --driver gecko --report auto;
add --appium-mode local only in local mode. Require
summary.requiredOk: true for server readiness, driver evidence, and
cleanup. The smoke reference documents target-specific options.
Gecko setup safety and approval constraints
- Ask before privileged package-manager commands or browser installation.
- Install an optional Firefox channel only when explicitly requested;
otherwise use an existing supported Firefox installation or report it
missing.
- Preserve the selected command mode and working Firefox and driver
installations.
Completion criteria
- Appium succeeds in the selected command mode with major version
>= 3.
- The installed driver list includes
gecko.
- At least one supported Firefox browser is available.
- Doctor reports
0 required fixes needed when supported; otherwise the
install, list, Firefox, and smoke gates pass.
/status succeeds and logs list gecko.
Evidence boundary
Report Appium and driver versions, Firefox executable and channel, helper and
doctor summaries, /status, server driver evidence, and cleanup.
Self-Improvement Prompt
Before the final response, report any missing, ambiguous, outdated, or
retry-causing Gecko setup instruction with its asset path and proposed wording.
Leave unrelated assets unchanged.
1---2name: setup-gecko3description: Prepare and verify Appium Gecko for Firefox desktop automation by validating Node/Appium, Firefox prerequisites, driver installation, optional GeckoDriver availability, doctor support, and server smoke evidence. Use after the setup Skill selects Gecko. Do not use for an existing Gecko runtime failure after prerequisites pass.4---56# Gecko Setup Workflow78## Routing910Prepare only the Appium Gecko route for Firefox desktop browsers. Use11driver-specific official guidance for an existing runtime failure after setup12passes.1314## Required inputs1516Confirm the Firefox channel or executable when non-default, global `appium`17mode or explicitly requested local `npx appium` mode, host OS, and permissions18for browser or package-manager changes.1920## Workflow21221. Load the global command profile by default or the local profile only when23 explicitly requested.242. Load the Gecko profile, shared Appium setup basics, Firefox prerequisites,25 and Gecko decision, driver-validation, and smoke references.263. Run `node tools/appium/setup/scripts/check-gecko-env.mjs --format summary --report auto`; add27 `--appium-mode local` only for explicitly requested local mode. Require28 top-level `summary.requiredOk: true`.29 Apply required fixes in technical dependency order and rerun affected checks.30 If the gate remains unresolved, report `blocked` with evidence and the next31 action. Load the matching example only when needed.324. Verify `appium driver doctor gecko` reports `0 required fixes needed`, or33 record `not-supported` and require the install, list, Firefox, and smoke34 gates instead. Use `npx --no-install appium ...` for the direct check in35 local mode.365. Run `node tools/appium/setup/scripts/smoke-appium-server.mjs --driver gecko --report auto`;37 add `--appium-mode local` only in local mode. Require38 `summary.requiredOk: true` for server readiness, driver evidence, and39 cleanup. The smoke reference documents target-specific options.4041## Gecko setup safety and approval constraints4243- Ask before privileged package-manager commands or browser installation.44- Install an optional Firefox channel only when explicitly requested;45 otherwise use an existing supported Firefox installation or report it46 missing.47- Preserve the selected command mode and working Firefox and driver48 installations.4950## Completion criteria5152- Appium succeeds in the selected command mode with major version `>= 3`.53- The installed driver list includes `gecko`.54- At least one supported Firefox browser is available.55- Doctor reports `0 required fixes needed` when supported; otherwise the56 install, list, Firefox, and smoke gates pass.57- `/status` succeeds and logs list `gecko`.5859## Evidence boundary6061Report Appium and driver versions, Firefox executable and channel, helper and62doctor summaries, `/status`, server driver evidence, and cleanup.6364## Self-Improvement Prompt6566Before the final response, report any missing, ambiguous, outdated, or67retry-causing Gecko setup instruction with its asset path and proposed wording.68Leave unrelated assets unchanged.