Name: dropbox-sign
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dropbox-sign

Dropbox Sign integration. Manage Accounts. Use when the user wants to interact with Dropbox Sign data.

Quality

63%

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/dropbox-sign/SKILL.md

Quality

Content

65%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 content is action-oriented and well-stocked with executable CLI commands and a useful actions table, making it strong on actionability. Its main gaps are the lack of validation before destructive actions and no progressive disclosure via reference files for the large actions catalog.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g. confirm with the user, or check signature-request status) before running delete-template or cancel-signature-request.

Move the 16-row Popular actions table and the detailed connection-state reference into a separate references/ file (e.g. ACTIONS.md) and link to it from SKILL.md to improve progressive disclosure.

Trim the introductory paragraph and the bare "Dropbox Sign Overview" entity bullets, which restate concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly command- and table-driven and reasonably lean, with only minor over-explanation (the introductory paragraph describing what Dropbox Sign is, and the "Dropbox Sign Overview" entity bullets) that could be trimmed; it does not reach 5 because of those padded passages.	4 / 5
Actionability	It provides concrete, executable Membrane CLI commands (login, connection ensure, action list/run, request) and a populated actions table; it stays at 4 rather than 5 because examples rely on placeholders (CONNECTION_ID, <actionId>, "QUERY", /path/to/endpoint) that require substitution.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state-based checkpoints and feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but the skill exposes destructive actions (delete-template, cancel-signature-request) with no validation or confirmation step before running them, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Section headers provide decent structure, but no bundle/reference files exist and the 16-row Popular actions catalog plus detailed connection-state reference are inlined in SKILL.md rather than split into separate files; it does not reach 4 because there are no one-level-deep references for the bulk material.	3 / 5
	Total	14 / 20 Passed

Description

62%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 correctly includes an explicit "Use when" trigger and names a distinct product, giving it solid completeness and distinctiveness. Its weaknesses are minimal action coverage (only "Manage Accounts", omitting signature requests) and generic trigger phrasing that misses common e-signature vocabulary.

Suggestions

Expand the "what" to name the primary capabilities, e.g. "Send and track signature requests, manage templates, and manage accounts" instead of only "Manage Accounts".

Add natural trigger terms users actually say, such as "e-signature", "sign documents", "signature request", or "send for signing".

Make the "when" clause more specific, e.g. "Use when the user wants to send or sign documents, track signature requests, or manage Dropbox Sign templates and teams."

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action ("Manage Accounts"), matching the anchor for 1-2 concrete actions that are not comprehensive; it does not reach 4 because it omits the skill's core capabilities (signature requests, templates, teams).	3 / 5
Completeness	Both a "what" ("Dropbox Sign integration. Manage Accounts.") and an explicit "when" ("Use when the user wants to interact with Dropbox Sign data.") are present; it stays at 4 rather than 5 because the "when" is generic and the "what" is incomplete.	4 / 5
Trigger Term Quality	It includes the strong product keyword "Dropbox Sign" and "Accounts", but misses common natural terms users would say (e.g. "sign documents", "e-signature", "signature request", "send for signing"), so it does not reach 4.	3 / 5
Distinctiveness Conflict Risk	The named product "Dropbox Sign" gives it a clear, distinct niche with minimal conflict risk; it does not reach 5 because the trigger phrasing "interact with Dropbox Sign data" is somewhat generic.	4 / 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/dropbox-sign/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.