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.
89
96%
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 strong skill description that concisely covers specific capabilities, includes natural trigger terms, and clearly delineates both what the skill does and when to use it. The description uses proper third-person voice and targets a distinct tool niche with minimal conflict risk.
| 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 via op') with explicit trigger scenarios. | 3 / 3 |
Trigger Term Quality | 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. | 3 / 3 |
Distinctiveness Conflict Risk | 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. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%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 a non-trivial workflow (1Password CLI via tmux sessions) with concrete, executable examples and clear validation checkpoints. The tmux requirement is well-justified and the guardrails provide important safety constraints around secret handling. The main weakness is that referenced files cannot be verified and the cross-reference to a separate tmux skill could be more explicit.
Suggestions
Provide the bundle files (references/get-started.md, references/cli-examples.md) or note their absence so the progressive disclosure structure can be fully validated.
Add a direct link or path to the referenced 'tmux skill' for socket conventions rather than assuming Claude will find it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what 1Password, tmux, and CLI tools are. Every section serves a purpose—no unnecessary explanations of what a CLI is or how secrets work. The tmux example is the longest section but is justified by the non-obvious TTY-per-command constraint. | 3 / 3 |
Actionability | Provides fully executable bash commands for the tmux session setup, sign-in, verification, and cleanup. The workflow steps include specific commands (`op --version`, `op signin`, `op whoami`) and the tmux block is copy-paste ready with proper socket/session management. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (check OS → verify CLI → confirm integration → create tmux → sign in → verify → handle multi-account). It includes explicit validation checkpoints (step 6: `op whoami` must succeed before proceeding) and error recovery guidance in Guardrails (re-run `op signin` if not signed in, stop and ask if tmux unavailable). | 3 / 3 |
Progressive Disclosure | References to `references/get-started.md` and `references/cli-examples.md` are clearly signaled and one level deep, which is good structure. However, no bundle files were provided, so we cannot verify these references exist or are accurate. The skill also references a `tmux` skill for socket conventions without a direct link, creating a potential navigation gap. | 2 / 3 |
Total | 11 / 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 | |
- Repository
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- Reviewed
Table of Contents
Is this your skill?
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.