1password
1Password integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1Password data.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/1password/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description benefits from targeting a specific product (1Password) and includes an explicit 'Use when' clause, which helps with completeness and distinctiveness. However, the actions described are vague ('manage data, records, and automate workflows') and could be much more concrete, and the trigger terms miss common user language around password management and secrets.
Suggestions
Replace vague actions with specific concrete capabilities, e.g., 'Retrieve passwords, create and update vault items, manage secure notes, share credentials, and automate secret rotation'.
Add natural trigger terms users would say, such as 'password manager', 'vault', 'secrets', 'credentials', 'login details', or 'API keys'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (1Password) and mentions some actions ('manage data, records, and automate workflows'), but these are fairly generic and not concrete specific actions like 'create vaults, retrieve passwords, share credentials, generate secure passwords'. | 2 / 3 |
Completeness | Answers both 'what' (manage data, records, automate workflows in 1Password) and 'when' (Use when the user wants to interact with 1Password data) with an explicit trigger clause, though both parts could be more detailed. | 3 / 3 |
Trigger Term Quality | Includes '1Password' as a strong trigger term and 'records' and 'workflows' as somewhat relevant keywords, but misses common natural terms users might say like 'password manager', 'vault', 'secrets', 'credentials', 'login', or 'password retrieval'. | 2 / 3 |
Distinctiveness Conflict Risk | 1Password is a very specific product, making this skill clearly distinguishable from other skills. The explicit mention of '1Password' creates a distinct niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with highly actionable CLI commands and a well-structured connection workflow with proper state handling. The main weaknesses are some unnecessary introductory explanation (Claude knows what 1Password is) and a few filler sections (the sparse Vault/Item/Tag overview). The content could be tightened by removing known-concept explanations and the vague overview section.
Suggestions
Remove the introductory paragraph explaining what 1Password is — Claude already knows this, and it wastes tokens.
Either flesh out the 'Vault > Item > Tag' overview with actionable detail or remove it entirely, as 'Use action names and parameters as needed' is too vague to be useful.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., ' 1Password is a password manager that securely stores passwords...' is something Claude already knows), and the overview section with bullet points for Vault/Item/Tag is vague filler. However, most of the content is reasonably efficient with concrete commands and useful tables. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and parameter placeholders. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The authentication flow handles both interactive and headless environments with clear fallback steps. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's somewhat monolithic for its length (~100+ lines of inline content). The reference to official docs is good, but there are no bundle files to offload detailed content like the proxy request options table or the full connection state machine details. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.