ov-layers/skills/steam/SKILL.md
Steam gaming client with gamescope. Use when working with Steam, gaming, or gamescope in containers.
npx skillsauth add overthinkos/overthink-plugins steamInstall 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 |
| Security | shm_size: 1g |
| Volume | steam-data -> ~/.local/share/Steam |
| Install files | tasks: |
| Variable | Value |
|----------|-------|
| STEAM_RUNTIME_PREFER_HOST_LIBRARIES | 0 |
steam (RPM, from RPM Fusion nonfree)gamescope (RPM, Fedora main repos)XWayland is provided by the base sway layer.
# image.yml — requires nvidia base (RPM Fusion nonfree via fedora-nonfree)
sway-browser-vnc-steam:
base: nvidia
layers:
- sway-desktop-vnc
- steam
Steam is an X11 application — it requires XWayland. The base sway config has xwayland disable for headless optimization. This layer installs a sway drop-in config at ~/.config/sway/config.d/xwayland.conf that enables XWayland.
Gamescope is a nested Wayland compositor for games. Use it in Steam launch options:
gamescope -W 1920 -H 1080 -r 60 -- %command%
Features: resolution spoofing, FSR/NIS upscaling, FPS limiting, HDR support.
Steam Guard requires interactive login. Connect via VNC desktop, launch Steam, and log in manually. Auth tokens persist in the steam-data volume for subsequent container restarts.
/ov-layers:sway — Wayland compositor (dependency)/ov-layers:sway-desktop-vnc — Desktop composition with VNC/ov-layers:cuda — NVIDIA GPU support (via nvidia base)Not used in any current image definition. Standalone gaming layer requiring a Sway desktop image.
Use when the user asks about:
/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)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.