ov-selkies/skills/chrome-sway/SKILL.md
Google Chrome running on Sway compositor via exec autostart with DevTools protocol. Use when working with Chrome in Sway, browser automation, or CDP in desktop containers.
npx skillsauth add overthinkos/overthink-plugins chrome-swayInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | sway |
| Layers (includes) | chrome |
| Install files | tasks:, chrome-sway.conf |
# image.yml -- typically included via sway-desktop composition
my-browser:
layers:
- chrome-sway
Part of /ov-selkies:sway-desktop composition.
Chrome is launched by Sway's exec directive (autostart) via chrome-wrapper. It is not a supervisord service -- Sway owns the Chrome process. This means:
exec chrome-wrapper in sway config).ov eval wl sway exec <image> chrome-wrapper to relaunch Chrome from outside the container. Do not use ov shell with bare swaymsg -- the shell may lack the correct SWAYSOCK path.browser-open helper auto-launches Chrome if it's not running (see /ov-selkies:chrome for details)./ov-selkies:sway -- compositor dependency/ov-selkies:chrome -- Chrome browser and DevTools (included via layers)/ov-selkies:sway-desktop -- composition that includes chrome-sway/ov-selkies:wayvnc -- VNC access to see Chrome desktopUse when the user asks about:
/ov-build:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov-build:eval — declarative testing (eval: block, ov eval image, ov eval live)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.