Name: dashlane
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

dashlane

Dashlane integration. Manage data, records, and automate workflows. Use when the user wants to interact with Dashlane data.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/dashlane/SKILL.md

Quality

Content

67%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 a well-structured, highly actionable guide to the Membrane CLI integration with a solid connection-state feedback loop. Its main weaknesses are an unnecessary intro explaining what Dashlane is, inconsistent step numbering in the connection workflow, and only implied verification of action results.

Suggestions

Drop the opening paragraph defining what Dashlane is; Claude already knows, so start directly with the integration overview.

Fix the step numbering (provide an explicit "1a"/"Step 1" and label "Step 2: Search and run actions") so the "skip to Step 2" references resolve.

Add a brief verification note after running actions (e.g. check the `output` field and handle non-zero/error states) to strengthen the feedback loop for vault-modifying operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but opens by explaining what Dashlane is ("Dashlane is a password manager and digital wallet application...") which Claude already knows, plus minor padding like "so you can focus on the integration logic rather than auth plumbing". This matches anchor 3 (mostly efficient with some unnecessary explanation) and does not reach 4 because of the concept re-explanation.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action run, request) plus a complete flags table. It sits at 4 rather than 5 because some examples rely on unfilled placeholders (CONNECTION_ID, QUERY, actionId) and the "Popular actions" section is thin/repetitive rather than covering concrete common cases.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced (install → authenticate → connect → poll for READY → search actions → run) with an explicit state-checking feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR). It does not reach 5 because step numbering is inconsistent (a "1b" with no "1a", references to "Step 2" that is not explicitly labeled) and action-result verification is only implied ("result is in the output field").	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references. No bundle files are present. It stays at 4 rather than 5 because reference-style material (the proxy flags table, popular-actions discovery) is inlined and the ~140-line length is at the edge of what would benefit from being split into a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

61%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 names a distinct domain and includes an explicit Use-when trigger, but the capability verbs ("manage data, records, automate workflows") are generic and it omits natural synonyms like "passwords", "vault", or "password manager". Tightening the action list and adding user-facing trigger terms would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Dashlane actions, e.g. "Retrieve vault items, generate passwords, and search secure notes."

Add natural trigger synonyms users would say: "Use when the user wants to manage passwords, access their Dashlane vault, or generate secure passwords."

Keep the explicit "Use when..." clause but pair it with the concrete actions rather than "interact with Dashlane data".

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the Dashlane domain but the actions are minimal and generic rather than concrete (no equivalent of "extract text, fill forms"). It sits below anchor 3 because the listed actions lack concrete specificity, and above 1 because the domain is clearly named.	2 / 5
Completeness	It provides both a "what" ("Manage data, records, and automate workflows") and an explicit "when" clause ("Use when the user wants to interact with Dashlane data"). It does not reach 5 because the "what" is somewhat vague and the trigger phrases are not as concrete as the anchor 5 example.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Dashlane data" includes the natural keyword "Dashlane" but misses common synonyms users would say ("passwords", "password manager", "vault", "secure notes"). This matches anchor 3 (some relevant keywords, missing common variations) and is below 4 due to the synonym gaps.	3 / 5
Distinctiveness Conflict Risk	Dashlane is a specific named application, and the trigger "interact with Dashlane data" carves out a clear niche with minimal overlap risk against other skills. Voice is third person with no first/second-person penalty.	5 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/dashlane/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.