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/running secrets via op.
97
Does it follow best practices?
Validation for skill structure
tmux session setup for op commands
Uses tmux for op
0%
66%
Socket dir env var
0%
100%
Fresh session name
0%
100%
tmux -S socket flag
0%
100%
op signin in tmux
0%
100%
op whoami before vault ops
0%
100%
op --version check
100%
100%
Session cleanup
0%
100%
No bare op calls
0%
50%
Desktop integration prerequisite
100%
100%
mkdir socket dir
0%
100%
Without context: $0.1866 · 57s · 11 turns · 16 in / 2,939 out tokens
With context: $0.4043 · 1m 24s · 24 turns · 27 in / 4,679 out tokens
Secure secret injection with op run/inject
op run or op inject used
100%
100%
op run env-file pattern
100%
100%
op inject template pattern
25%
100%
Template uses op:// URIs
100%
100%
No plaintext secrets in files
100%
100%
op commands inside tmux
0%
0%
Fresh tmux session name
0%
0%
Socket dir convention
0%
0%
op whoami before secrets
0%
50%
deploy-notes explains approach
100%
100%
Without context: $0.3802 · 1m 33s · 22 turns · 28 in / 5,147 out tokens
With context: $0.4649 · 1m 49s · 26 turns · 29 in / 5,821 out tokens
Multi-account and non-integration auth
--account flag or OP_ACCOUNT
100%
100%
op account add for no-integration
100%
100%
op signin inside tmux
0%
0%
No bare op calls
0%
0%
Fresh timestamped session names
0%
0%
Socket dir env var
0%
0%
op whoami before data ops
0%
12%
Auth error recovery
37%
50%
op --version check
100%
100%
Desktop integration steps
50%
100%
Two accounts demonstrated
100%
100%
mkdir socket dir
0%
0%
Without context: $0.2846 · 1m 35s · 12 turns · 14 in / 5,635 out tokens
With context: $0.4236 · 1m 46s · 22 turns · 59 in / 5,853 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.