Lists multiple specific concrete actions: installing the CLI, enabling desktop app integration, signing in (single or multi-account), reading/injecting/running secrets via op. These are distinct, actionable capabilities.

Clearly answers both what ('Set up and use 1Password CLI') and when ('Use when installing the CLI, enabling desktop app integration, signing in, or reading/injecting/running secrets via op') with explicit trigger scenarios.

Includes strong natural keywords users would say: '1Password', 'CLI', 'op', 'secrets', 'signing in', 'desktop app integration', 'injecting'. Covers the tool name, command name, and common use cases users would mention.

Highly distinctive — 1Password CLI (op) is a very specific tool with a clear niche. The triggers are unlikely to conflict with other skills unless there's another 1Password-related skill.

The content is lean and efficient. It doesn't explain what 1Password is or how CLIs work. Every section serves a purpose—workflow steps, tmux requirement, guardrails—with no padding or unnecessary context.

Provides fully executable bash commands for the tmux session setup, sign-in, verification, and cleanup. The workflow steps include specific commands like `op --version`, `op signin`, `op whoami`. The tmux example is copy-paste ready with proper socket/session handling.

Clear numbered sequence with explicit validation checkpoints: verify CLI present (step 2), confirm integration enabled (step 3), verify access with `op whoami` must succeed before proceeding (step 6). Error recovery is addressed in guardrails (re-run signin if not signed in). The tmux requirement is clearly marked as mandatory with rationale.

Clean overview structure with references to `get-started.md` and `cli-examples.md` for detailed content, plus a reference to the `tmux` skill for socket conventions. All references are one level deep and clearly signaled. The SKILL.md itself stays focused on the workflow and essential patterns.