test-skill22131

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/...

Security Scan

The skill's description, install, and required binary (op) line up with a 1Password CLI helper, but the runtime instructions include actions (capturing tmux pane output, using socket dirs via undeclared env vars) that could inadvertantly collect or expose secrets and are not fully justified or constrained.

Purpose & Capability

Name, description, required binary (op), and the brew install formula (1password-cli) are consistent with a skill whose job is to help install and use the 1Password CLI.

Instruction Scope

The SKILL.md mandates running every op command inside a freshly-created tmux session and explicitly captures the tmux pane (capture-pane) then kills the session. Capturing terminal output can include secrets (or one-time codes) and the instructions do not require redaction or otherwise limit what is captured or how the captured output is handled/transmitted. The instructions also reference socket-directory env vars (OPENCLAW_TMUX_SOCKET_DIR, CLAWDBOT_TMUX_SOCKET_DIR) that are not declared in the skill metadata. Overall the instructions perform actions that could expose sensitive data unless callers strictly follow additional safeguards not specified here.

Install Mechanism

Install spec uses Homebrew formula '1password-cli' which is an expected, low-risk installation path for this purpose. No arbitrary downloads or archive extraction are present.

Credentials

The skill declares no required credentials or env vars (appropriate for a local CLI helper). However, it references OPENCLAW_TMUX_SOCKET_DIR and CLAWDBOT_TMUX_SOCKET_DIR in example commands; these are not declared in requires.env. There is no request for unrelated credentials, which is good.

Persistence & Privilege

The skill is not force-included (always: false) and does not request elevated or persistent platform privileges. Autonomous invocation is allowed by platform default but not combined with other high-risk flags.

What to consider before installing

This skill appears to be a legitimate 1Password CLI helper and installs via Homebrew as expected. The main risk is operational: the instructions require creating a tmux session and capturing the terminal pane, which can include sensitive output. Before installing, confirm you (or the agent) will: 1) never transmit captured pane output to logs or external services, 2) implement redaction or strict filtering of captured output, and 3) review/declare any socket-related env vars (OPENCLAW_TMUX_SOCKET_DIR / CLAWDBOT_TMUX_SOCKET_DIR) used in your environment. If you want stronger guarantees, ask the skill author to remove automatic capture-pane usage or to add explicit redaction and handling rules in SKILL.md. If these safeguards cannot be enforced, treat outputs from this skill as high-sensitivity data and restrict its use.

1Password CLI

Follow the official CLI get-started steps. Don't guess install commands.

References

• references/get-started.md (install + app integration + sign-in flow)
• references/cli-examples.md (real op examples)

Workflow

1. Check OS + shell.
2. Verify CLI present: op --version.
3. Confirm desktop app integration is enabled (per get-started) and the app is unlocked.
4. REQUIRED: create a fresh tmux session for all op commands (no direct op calls outside tmux).
5. Sign in / authorize inside tmux: op signin (expect app prompt).
6. Verify access inside tmux: op whoami (must succeed before any secret read).
7. If multiple accounts: use --account or OP_ACCOUNT.

REQUIRED tmux session (T-Max)

The shell tool uses a fresh TTY per command. To avoid re-prompts and failures, always run op inside a dedicated tmux session with a fresh socket/session name.

Example (see tmux skill for socket conventions, do not reuse old session names):

SOCKET_DIR="${OPENCLAW_TMUX_SOCKET_DIR:-${CLAWDBOT_TMUX_SOCKET_DIR:-${TMPDIR:-/tmp}/openclaw-tmux-sockets}}"
mkdir -p "$SOCKET_DIR"
SOCKET="$SOCKET_DIR/openclaw-op.sock"
SESSION="op-auth-$(date +%Y%m%d-%H%M%S)"

tmux -S "$SOCKET" new -d -s "$SESSION" -n shell
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op signin --account my.1password.com" Enter
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op whoami" Enter
tmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op vault list" Enter
tmux -S "$SOCKET" capture-pane -p -J -t "$SESSION":0.0 -S -200
tmux -S "$SOCKET" kill-session -t "$SESSION"

Guardrails

• Never paste secrets into logs, chat, or code.
• Prefer op run / op inject over writing secrets to disk.
• If sign-in without app integration is needed, use op account add.
• If a command returns "account is not signed in", re-run op signin inside tmux and authorize in the app.
• Do not run op outside tmux; stop and ask if tmux is unavailable.