CtrlK
BlogDocsLog inGet started
Tessl Logo

bitwarden

Bitwarden integration. Manage security and password-management data, records, and workflows. Use when the user wants to interact with Bitwarden data.

61

Quality

72%

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/bitwarden/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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 with complete, executable Membrane CLI commands and a solid connection-state feedback loop, but it opens with unnecessary background on what Bitwarden is and provides no validation steps for destructive vault operations.

Suggestions

Remove or trim the introductory paragraph and 'Bitwarden Overview' section — Claude already knows what Bitwarden and vaults/items are.

Add a validation/check step before running destructive actions (e.g., deleting or overwriting vault items), such as listing the target item and confirming with the user first.

Consider moving the proxy-request flag table and connection-state reference into a separate reference file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete CLI commands, but the opening paragraph ('Bitwarden is an open source password manager...used by individuals, teams, and businesses') and the generic Vault/Items/Organizations overview explain concepts Claude already knows, which the rubric penalizes.

3 / 5

Actionability

Copy-paste-ready commands cover the common cases end to end — install, login (interactive and headless), connection ensure, polling, action list/run with JSON inputs, and proxy requests with a full flag table — fully executable guidance.

5 / 5

Workflow Clarity

The connection setup has an explicit feedback loop (poll state → handle READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR → re-poll), but there is no validation guidance for destructive action runs against vault data, leaving a minor checkpoint gap.

4 / 5

Progressive Disclosure

No bundle files exist, so all content is inline in a single well-organized file with clear section headers and no nested references; structure is good though ~100 lines of CLI detail could arguably be split into a reference file.

4 / 5

Total

16

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 clearly names the Bitwarden niche and includes an explicit 'Use when' trigger, but relies on generic verbs ('manage', 'interact') and omits the most natural user terms ('passwords', 'vault', 'credentials'). It is solid but not comprehensive.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Create, search, share, and rotate vault items and credentials in Bitwarden.'

Add natural trigger terms users actually say — 'passwords', 'vault', 'credentials', 'password manager' — to the 'Use when' clause.

Make the 'when' clause more concrete: 'Use when the user wants to manage passwords, vault items, or shared credentials in Bitwarden.'

DimensionReasoningScore

Specificity

Names the domain ('security and password-management data, records, and workflows') but the verbs are generic ('Manage', 'interact') rather than concrete actions like create, share, or rotate credentials, fitting the '1-2 actions but not comprehensive' anchor.

3 / 5

Completeness

Both 'what' ('Manage security and password-management data, records, and workflows') and 'when' ('Use when the user wants to interact with Bitwarden data') are present, but the trigger phrase is generic rather than enumerating concrete triggers, so it falls short of the level-5 anchor.

4 / 5

Trigger Term Quality

Good keyword coverage with 'Bitwarden', 'security', 'password-management', and 'interact with Bitwarden data', but it misses common natural terms users say such as 'passwords', 'vault', 'credentials', or 'password manager'.

4 / 5

Distinctiveness Conflict Risk

The named product 'Bitwarden' gives it a clear niche with minimal conflict risk, though the broad 'security' framing leaves minor overlap risk with other security/password skills.

4 / 5

Total

15

/

20

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
membranedev/application-skills
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.