ov-layers/skills/ssh-client/SKILL.md
OpenSSH client tools for SSH agent forwarding. Use when working with SSH client, SSH agent forwarding, or the ssh-client layer.
npx skillsauth add overthinkos/overthink-plugins ssh-clientInstall 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 (packages only) |
RPM: openssh-clients · PAC: openssh · DEB: openssh-client (singular — Debian splits client/server, unlike Arch's unified openssh).
Note: On Arch Linux, openssh is a single package that includes both client and server. The sshd layer also installs this package but adds a systemd service and opens port 22. On Debian/Ubuntu, openssh-client ships only the client tools; openssh-server is a separate package installed by the sshd layer.
# image.yml
my-image:
layers:
- ssh-client
Typically used as part of the agent-forwarding composition layer rather than directly. Use the sshd layer instead if you need an SSH server.
Provides ssh, ssh-add, ssh-keygen, ssh-agent, scp, sftp binaries. When combined with SSH agent forwarding (ov shell, ov start direct mode), the container's SSH commands use the host's SSH agent via a forwarded socket at /run/host-ssh-auth.sock.
No SSH agent runs inside the container — the SSH_AUTH_SOCK environment variable points to the forwarded host socket.
Part of agent-forwarding composition layer, used in 27 application images.
/ov-layers:agent-forwarding -- metalayer that includes gnupg + direnv + ssh-client/ov-layers:sshd -- SSH server + client (includes systemd service, port 22)/ov-layers:gh -- GitHub CLI + git (uses SSH for git operations)Use when the user asks about:
ssh-client layerssh-client and sshd layers/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)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).