ov-vms/skills/openclaw-browser-bootc-bootc/SKILL.md
kind:vm entity pairing with the /ov-openclaw:openclaw-browser-bootc container image. source.kind: bootc. Thin pointer skill — composition + layer stack authority lives in /ov-openclaw:openclaw-browser-bootc. This skill documents only VM overrides. MUST be invoked before editing openclaw-browser-bootc-bootc in vms.yml.
npx skillsauth add overthinkos/overthink-plugins openclaw-browser-bootc-bootcInstall 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.
kind: vm entity that pairs with the /ov-openclaw:openclaw-browser-bootc container image. The doubled -bootc suffix reflects that the paired image already ends in -bootc — the VM entity is distinguished by the vms: namespace, not by its name.
Composition authority: /ov-openclaw:openclaw-browser-bootc. OpenClaw gateway, Chrome, VNC, PipeWire composition, OCI labels all live there. This skill is a pointer.
vms:
openclaw-browser-bootc-bootc:
source:
kind: bootc
image: openclaw-browser-bootc
disk_size: 20 GiB
ram: 4G
cpus: 2
ssh:
user: root
port: 2222
| Setting | Value | Rationale |
|---|---|---|
| Disk size | 20 GiB | Minimal bootc install + Chrome + VNC; tighter than desktop-class VMs |
| RAM | 4G | Browser + VNC fits in 4 GiB for a kiosk-style workload |
| CPUs | 2 | Conservative; Chrome + compositor don't need more |
| SSH user | root | bootc default; no non-root base user created |
| SSH port | 2222 | Standard — only collision risk is with other VMs on 2222 |
Firmware, machine, network default to VmSpec defaults (see /ov-vms:vms).
# Enable openclaw-browser-bootc in image.yml first (disabled by default)
ov image build openclaw-browser-bootc
ov vm build openclaw-browser-bootc-bootc
ov vm create openclaw-browser-bootc-bootc
ov vm start openclaw-browser-bootc-bootc
ssh -p 2222 root@localhost
/ov-openclaw:openclaw-browser-bootc — composition authority: layer stack, OpenClaw gateway, Chrome, VNC, OCI labels/ov-vms:vms — VmSpec authoring reference, bootc branch authoring recipe/ov-advanced:vm — VM lifecycle commands + bootc-specific caveats/ov-build:migrate — ov migrate vm-spec legacy conversion/ov-openclaw:openclaw — OpenClaw gateway layertools
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).