overthinkos/chrome-sway
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.
tools
Updated Jun 28, 2026
$ install --global
skillsauthnpx skillsauth add overthinkos/overthink-plugins chrome-swayInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 28, 2026, 5:57 AM157.4s1 file scanned
SKILL.md
- name:
- chrome-sway
- description:
- |
chrome-sway -- Chrome browser on Sway compositor
Candy Properties
| Property | Value |
|----------|-------|
| Dependencies | sway |
| Candies (includes) | chrome |
| Install files | task:, chrome-sway.conf |
Usage
# charly.yml -- typically included via sway-desktop composition
my-browser:
candy:
- chrome-sway
Used In Boxes
Part of /charly-selkies:sway-desktop composition.
Chrome Lifecycle in Sway
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:
- Autostart: Chrome starts when Sway starts (via
exec chrome-wrapperin sway config). - Crashes/exits: Chrome does not auto-restart. If Chrome exits, it must be relaunched manually.
- Manual restart: Relaunch Chrome with a
wl: execstep runningchrome-wrapper(thewl:verb dispatches out-of-process via candy/plugin-wl). Do not usecharly shellwith bareswaymsg-- the shell may lack the correctSWAYSOCKpath. - On-demand launch: The
browser-openhelper auto-launches Chrome if it's not running (see/charly-selkies:chromefor details).
Related Candies
/charly-selkies:sway-- compositor dependency/charly-selkies:chrome-- Chrome browser and DevTools (included via candies)/charly-selkies:sway-desktop-- composition that includes chrome-sway/charly-selkies:wayvnc-- VNC access to see Chrome desktop
When to Use This Skill
Use when the user asks about:
- Chrome running in Sway desktop
- Browser autostart in compositor
- CDP (Chrome DevTools Protocol) in desktop containers
- Chrome-sway configuration
Related
/charly-image:layer— candy authoring reference (charly.ymlschema, task verbs, service declarations)/charly-check:check— declarative testing (check:block,charly check box,charly check live)
Related Skills
overthinkos/plugin
tools
VerifiedTrustedCommunity
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
SKILL.mdUpdated Jun 22, 2026
overthinkos/cue
tools
VerifiedTrustedCommunity
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
SKILL.mdUpdated Jun 16, 2026
overthinkos/egress
tools
VerifiedTrustedCommunity
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
SKILL.mdUpdated Jun 16, 2026
overthinkos/check-k8s
tools
VerifiedTrustedCommunity
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).
SKILL.mdUpdated Jun 14, 2026