CtrlK
BlogDocsLog inGet started
Tessl Logo

1password

Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/1password/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-structured, with explicit validation checkpoints, an error-recovery feedback loop, and one-level-deep references to real bundle files. The only drag is conciseness, hurt by the irrelevant PilotDeck migration note and socket boilerplate that could be trimmed.

Suggestions

Remove the "PilotDeck Migration Note" section; it is review/migration metadata unrelated to using the skill and adds context noise that does not earn its tokens.

Tighten the tmux socket-setup boilerplate — extract a reusable snippet or trim the inline socket/session setup so the example earns every token while staying executable.

Move or summarize the per-OS desktop-integration detail (already in references/get-started.md) out of the main workflow if it duplicates the reference, keeping SKILL.md as a true overview.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the "PilotDeck Migration Note" is review/migration metadata unrelated to skill usage and the tmux socket boilerplate could be tightened, matching the anchor for mostly efficient content with some unnecessary padding.

2 / 3

Actionability

It provides concrete commands (op --version, op signin, op whoami, --account/OP_ACCOUNT) plus a complete, copy-paste-ready tmux bash block, matching the anchor for fully executable, copy-paste-ready guidance.

3 / 3

Workflow Clarity

Seven sequenced steps include explicit validation checkpoints (op --version; "op whoami must succeed before any secret read") and an error-recovery feedback loop (re-run op signin on "account is not signed in"), matching the anchor for clear sequence with validation and feedback loops.

3 / 3

Progressive Disclosure

The References section clearly signals two real, one-level-deep files with parenthetical descriptions, and content is appropriately split between the overview, install/integration details, and the example catalog, matching the anchor for a clear overview with well-signaled one-level-deep references.

3 / 3

Total

11

/

12

Passed

Description

67%

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 names concrete actions and occupies a clear, low-conflict niche, but it lacks an explicit "Use when..." trigger clause and omits common natural terms like "password," "op," or "credentials." Adding explicit trigger guidance would raise the two lowest dimensions.

Suggestions

Add an explicit "Use when..." clause naming triggers, e.g. "Use when the user needs to sign in to 1Password, read or inject passwords/secrets, or set up the op CLI."

Include natural trigger terms users would actually say — "password," "credentials," and "op CLI" — alongside "secrets" and "sign-in" to improve trigger term coverage.

Consider dropping or softening the jargon term "desktop integration" in favor of a user-facing phrase such as "connect the 1Password app."

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "set up," "sign-in," "desktop integration," and "reading or injecting secrets" — matching the anchor for listing multiple specific concrete actions rather than naming only a domain and one action.

3 / 3

Completeness

It clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant keywords like "1Password CLI," "sign-in," and "secrets" are present, but common natural variations users would say ("password," "op," "credentials") are missing and "desktop integration" leans toward jargon.

2 / 3

Distinctiveness Conflict Risk

"1Password CLI" is a clear niche with distinct triggers that is unlikely to overlap with or be confused for other skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
OpenBMB/PilotDeck
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.