CtrlK
BlogDocsLog inGet started
Tessl Logo

double

Double (formerly Keeper) integration. Manage data, records, and automate workflows. Use when the user wants to interact with Double (formerly Keeper) data.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/double/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 executable Membrane CLI commands and a well-sequenced, validated connection workflow. It is slightly held back by an inlined action reference table and minor verbosity in a few explanatory clauses.

Suggestions

Move the large Popular actions table into a separate references file and link to it from the body.

Add a verification step after running or proxying actions (e.g. inspect the `output` field, handle non-2xx responses).

Trim explanatory filler such as "so you can focus on the integration logic rather than auth plumbing".

DimensionReasoningScore

Conciseness

The body is mostly lean command examples with brief context; only minor clauses (e.g. "so you can focus on the integration logic rather than auth plumbing") could be trimmed.

4 / 5

Actionability

Copy-paste ready commands cover the common cases (install, login, connection ensure/get, action list/run, request proxy) with flags, JSON output, and parameter passing explicitly shown.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with explicit state checks and a poll-until-ready feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED), though running and proxying actions lack verification steps.

4 / 5

Progressive Disclosure

Sections are well organized with clear headers and no nested references, but the sizable Popular actions table is inlined in SKILL.md rather than split into a separate reference file.

4 / 5

Total

17

/

20

Passed

Description

73%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 cleanly identifies the named product and includes an explicit 'Use when' trigger, but the capability description leans on generic verbs. It is distinct and triggerable, just not richly specific.

Suggestions

Replace generic verbs ("Manage", "automate") with concrete actions such as list, create, update, and delete records/clients/tasks.

Add natural trigger synonyms users might say, e.g. vaults, passwords, contacts, or client tasks.

Tighten the 'when' clause to name the concrete entities users interact with rather than just 'data'.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the domain plus a couple of actions, but the verbs (manage, automate) are generic and coverage is not comprehensive, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Double (formerly Keeper) data"), but the 'what' is somewhat generic and the 'when' could be more specific.

4 / 5

Trigger Term Quality

Trigger references "Double (formerly Keeper)" with both current and legacy product names plus "data" and "records", giving good keyword coverage; a few natural synonyms (e.g. vault, password) are missing.

4 / 5

Distinctiveness Conflict Risk

Tied to a named product ("Double (formerly Keeper)"), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

16

/

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.