Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Installs and configures the 1Password CLI (`op`) for reading, injecting, and running secrets from a 1Password vault. Handles authentication flows including desktop app integration and multi-account setups. All `op` commands run inside a dedicated tmux session to avoid TTY re-prompt failures.
`op run` and `op inject` keep secrets out of env files and shell history entirely, unlike manually exporting variables.
When to use it
- Injecting API keys into a dev server without writing them to disk
- Running a script with secrets via `op run` in CI-like workflows
- Switching between multiple 1Password accounts using `--account`
- Verifying vault access and listing available vaults after sign-in
- Automating secret retrieval inside tmux for shell-tool environments
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: run my deploy script with production secrets from 1Password
- 1Verify `op --version` confirms CLI is installed
- 2Create a fresh tmux session with a unique socket and session name
- 3Run `op signin` inside tmux and wait for desktop app authorization
- 4Confirm access with `op whoami` before proceeding
- 5Execute `op run -- ./deploy.sh` inside the tmux session to inject secrets at runtime
Deploy script runs with secrets injected via `op run`, nothing written to disk or logs
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.