Agent skill · software engineering · sundial-org
1password
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.
Why this skill is useful
Adds a comprehensive executable script for managing 1Password CLI sessions with tmux, which is not commonly documented.
What it needs
Requires 1password-cli, tmux installed locally. Requires 1password account access. About 1k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
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 OPACCOUNT. 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): 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/1password