Lean body with no padding or explanation of concepts Claude already knows; the only prose (the tmux rationale) earns its place by justifying the REQUIRED pattern, matching the 'lean and efficient; every token earns its place' anchor.

Provides executable commands (`op --version`, `op signin`, `op whoami`) and a complete, copy-paste-ready tmux bash block with real socket/session setup; above level 2 because it is fully executable rather than pseudocode.

A clearly sequenced 7-step workflow with an explicit validation checkpoint ('op whoami must succeed before any secret read') and an error-recovery feedback loop in Guardrails ('re-run op signin inside tmux'); exceeds the level-2 anchor that lacks checkpoints.

Body is an overview with a References section pointing to two verified, one-level-deep files (get-started.md and cli-examples.md), each labeled with its contents and appropriately split (install/integration vs. examples); matches the 'clear overview with well-signaled one-level-deep references' anchor.

Lists multiple concrete actions — 'installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op' — rather than vague language; matches the 'lists multiple specific concrete actions' anchor and exceeds the level-2 single-domain example.

Explicitly answers what ('Set up and use 1Password CLI (op)') and when via a 'Use when...' clause enumerating triggers; the explicit trigger guidance lifts it above the level-2 anchor where 'when' is only implied.

Uses natural terms a user would say ('1Password CLI', 'op', 'signing in', 'desktop app integration', 'secrets') with good coverage including the 'op' shorthand, not just jargon; not below 3 because common variations are present.

Scoped narrowly to 1Password CLI/op with distinct triggers, unlikely to fire for unrelated skills; clearer niche than the level-2 'Works with document files' example.