Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use the ssh-op helper script to load an SSH private key from 1Password (op) into an in-memory ssh-agent and then run ssh. Use when connecting to hosts that r...
Use the ssh-op helper script to load an SSH private key from 1Password (op) into an in-memory ssh-agent and then run ssh. Use when connecting to hosts that r...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
ssh-op is a wrapper around ssh that: ensures an ssh-agent exists for the current shell loads an SSH key from 1Password via op read ... | ssh-add - then execs ssh with your arguments
Fail-fast checks you can run: command -v op ssh ssh-agent ssh-add op whoami If op whoami fails: Sign in to 1Password CLI (desktop integration / account sign-in), or If using a service account flow, ensure OP_SERVICE_ACCOUNT_TOKEN is set.
Machine-specific config lives alongside the skill: Example (do not edit): ~/.openclaw/skills/ssh-op/config.env.example Real (machine-specific): ~/.openclaw/skills/ssh-op/config.env Required keys: SSH_OP_VAULT_NAME โ 1Password vault containing the key SSH_OP_ITEM_TITLE โ 1Password item title Optional keys: SSH_OP_KEY_FIELD โ defaults to private key SSH_OP_KEY_FINGERPRINT_SHA256 โ if set, skip re-loading when already in ssh-agent SSH_OP_HOSTS_FILE โ defaults to hosts.conf (ssh config snippet filename) SSH host entries (optional) live in: ~/.openclaw/skills/ssh-op/hosts.conf
Because the primary interface is chat (Telegram), the preferred onboarding flow is: Ask Boss the required questions in chat. Write the real config file: config.env. Run a smoke test (e.g. ssh-op --help and a safe ssh-op -T <alias>).
If you are running in a real terminal, you can use the interactive onboarding script: ~/.openclaw/skills/ssh-op/scripts/onboard.sh (If you want a step-by-step runbook, see references/onboarding.md.)
Canonical executable lives inside the skill: ~/.openclaw/skills/ssh-op/scripts/ssh-op For convenience, create a symlink: mkdir -p ~/.local/bin ln -sf ~/.openclaw/skills/ssh-op/scripts/ssh-op ~/.local/bin/ssh-op
Run onboarding to populate the real config: ~/.openclaw/skills/ssh-op/scripts/onboard.sh (Or edit config.env manually and set SSH_OP_VAULT_NAME / SSH_OP_ITEM_TITLE.) Then validate: ssh-op --help # try a safe ssh command (or any host alias you have configured) ssh-op -T <host-alias>
Put desired Host entries in hosts.conf Apply them idempotently (adds/updates a managed block): ~/.openclaw/skills/ssh-op/scripts/ensure_ssh_config.py This will update ~/.ssh/config between: # BEGIN ssh-op (managed) # END ssh-op (managed)
ssh-op <ssh-args...> Examples: ssh-op my-host-alias ssh-op -T my-host-alias ssh-op -L 8080:localhost:8080 my-host-alias
No private key is written to disk. ssh-agent lifetime is tied to the current shell unless you export SSH_AUTH_SOCK / SSH_AGENT_PID.
Keep the canonical executable in the skill folder (scripts/ssh-op). Use a symlink (e.g. ~/.local/bin/ssh-op) for convenience.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.