hermes/skills/hermes-playwright-layer/SKILL.md
Playwright Chromium browser for Hermes Agent with Fedora-compatible system deps. MUST be invoked before any work involving: Playwright in hermes containers, Chromium browser automation for hermes, or hermes-playwright candy configuration.
npx skillsauth add overthinkos/overthink-plugins hermes-playwright-layerInstall 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 | hermes |
| Security | shm_size: 1g |
| Install files | charly.yml, package.json, task: |
| RPM packages | alsa-lib, at-spi2-core, cups-libs, gtk3, libdrm, libxkbcommon, nss, mesa-dri-drivers, vulkan-loader, libXcomposite, libXdamage, libXrandr, pango, cairo |
| Variable | Value |
|----------|-------|
| PLAYWRIGHT_BROWSERS_PATH | /tmp/.cache/ms-playwright |
This is a Tier 1 candy (no pixi.toml) that adds Playwright + Chromium on top of the hermes candy.
Playwright's npx playwright install --with-deps does not support Fedora -- it falls back to Ubuntu and tries apt-get, which fails. The workaround:
charly.yml install all Chromium system library dependencies manuallycmd: task runs npx playwright install chromium (without --with-deps) to download only the browser binaryBrowsers are installed to /tmp/.cache/ms-playwright/ during the build (the cmd runs as root with HOME=/tmp). The PLAYWRIGHT_BROWSERS_PATH env var ensures Playwright finds them at runtime.
The Playwright npm package is installed globally via the npm builder (from package.json). To require('playwright') in Node.js, set NODE_PATH:
NODE_PATH=~/.npm-global/lib/node_modules node -e "const { chromium } = require('playwright'); ..."
Or use the npx CLI directly:
npx playwright --version
# charly.yml
hermes-playwright:
base: fedora
candy:
- agent-forwarding
- hermes
- hermes-playwright
- dbus
- charly
/charly-hermes:hermes-playwright -- hermes with Playwright Chromium/charly-hermes:hermes -- base hermes agent (required dependency)/charly-selkies:chrome -- similar pattern for Chrome system deps/charly-hermes:playwright-layer -- OpenClaw's Playwright layer (npm only, no Chromium binary)MUST be invoked when the task involves Playwright browser automation in hermes containers, Chromium system dependencies on Fedora, or the hermes-playwright candy. Invoke this skill BEFORE reading source code or launching Explore agents.
/charly-image:layer — candy authoring reference (charly.yml schema, task verbs, service declarations)/charly-check:check — declarative testing (check: block, charly check box, charly check live)tools
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.
tools
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.
tools
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).
tools
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).