Claude Agent Skill · by Steipete

1password

Install 1password skill for Claude Code from steipete/clawdis.

Install
Terminal · npx
$npx skills add https://github.com/anthropics/skills --skill pdf
Works with Paperclip

How 1password fits into a Paperclip company.

1password drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md70 lines
Expand
---name: 1passworddescription: 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.homepage: https://developer.1password.com/docs/cli/get-started/metadata:  {    "openclaw":      {        "emoji": "🔐",        "requires": { "bins": ["op"] },        "install":          [            {              "id": "brew",              "kind": "brew",              "formula": "1password-cli",              "bins": ["op"],              "label": "Install 1Password CLI (brew)",            },          ],      },  }--- # 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): ```bashSOCKET_DIR="${OPENCLAW_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 shelltmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op signin --account my.1password.com" Entertmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op whoami" Entertmux -S "$SOCKET" send-keys -t "$SESSION":0.0 -- "op vault list" Entertmux -S "$SOCKET" capture-pane -p -J -t "$SESSION":0.0 -S -200tmux -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.