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.
91
Quality
100%
Does it follow best practices?
Impact
69%
1.86xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that follows best practices. It uses third person voice, provides specific concrete actions, includes an explicit 'Use when...' clause with multiple trigger scenarios, and has distinctive terminology (1Password, op) that clearly identifies its niche. The description efficiently communicates both capabilities and usage triggers in a concise format.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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. | 3 / 3 |
Completeness | 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'). Has explicit 'Use when...' clause with specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: '1Password', 'CLI', 'op', 'secrets', 'signing in', 'desktop app integration'. Covers both the product name and the command-line tool name (op) that users would reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around 1Password CLI specifically. The combination of '1Password', 'op', and specific operations like 'injecting secrets' creates a unique fingerprint unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently communicates the 1Password CLI workflow with executable code, clear validation steps, and appropriate references. The tmux requirement is thoroughly explained with copy-paste ready code, and guardrails provide important safety constraints without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude knows what 1Password, tmux, and CLI tools are. No unnecessary explanations of basic concepts; every section serves a clear purpose. | 3 / 3 |
Actionability | Provides fully executable bash code for the tmux session workflow, specific commands like `op signin`, `op whoami`, and `op vault list`, plus clear references to detailed documentation for edge cases. | 3 / 3 |
Workflow Clarity | Clear numbered sequence with explicit validation checkpoints (step 6: 'must succeed before any secret read'), error recovery guidance ('If sign-in without app integration is needed...'), and explicit constraints about tmux requirements. | 3 / 3 |
Progressive Disclosure | Concise overview with well-signaled one-level-deep references to `references/get-started.md` and `references/cli-examples.md`. Content is appropriately split between quick workflow and detailed reference materials. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
50ef2f3
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.