ov-layers/skills/socat/SKILL.md
Socket relay tool for VM console access and port relays (eth0 to loopback). Use when working with port relays, socat, or loopback service exposure.
npx skillsauth add overthinkos/overthink-plugins socatInstall 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 |
|----------|-------|
| Install files | layer.yml, tasks: |
RPM: socat, iproute
rpm: (Fedora), pac: (Arch), deb: (Debian/Ubuntu — socat, iproute2). Full parity.
# image.yml
my-image:
layers:
- socat
Typically not added directly. Auto-included when a layer uses port_relay: in its layer.yml.
Note: Chrome no longer uses socat for its DevTools port relay. Chrome now uses a cdp-proxy Python supervisord service (see /ov-layers:chrome). Socat is still used by other port_relay consumers.
ov-full composition layer (used in githubrunner)/ov-layers:virtualization -- part of ov-full alongside socat/ov-layers:gocryptfs -- part of ov-full alongside socatUse when the user asks about:
socat layer or port_relay field/ov:layer — layer authoring reference (tasks, vars, env_provides, tests block syntax)/ov:test — declarative testing framework for the tests: blockdevelopment
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.