ssh-access-manager

What problem does it solve?

It removes friction and mistakes in how workbench users reach the correct target containers over SSH sidecars, especially when ForceCommand routing, zmx menu/profile attachment, and in-cluster kubectl hops must stay deterministic.

Core Features & Use Cases

• SSH sidecar ForceCommand wiring: Ensures SSH requests are routed through the correct wrapper entrypoint with predictable behavior.
• Wrapper-based container hop & guardrails: Uses helper logic to move from the SSH sidecar to the appropriate target container and keeps non-interactive passthrough consistent via SSH_ORIGINAL_COMMAND semantics.
• Deterministic zmx profile and shared-session conventions: Standardizes profile naming, shared attach behavior, and shortcut attachment rules so operators land in the intended session.
• Use Case: When multiple workbench agent kinds (codex, gemini, gemini-secondary, claude) must be accessed from the same SSH sidecar, this skill guarantees the correct container and session/profile are selected and attached without relying on ad-hoc operator steps.

Quick Start

Use the ssh-access-manager skill to set up SSH sidecar ForceCommand routing for a workbench agent kind by ensuring the sidecar runs prepare-ssh-config with the desired agent-kind.