Name: dropbox
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dropbox

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

Quality

68%

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

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 executable Membrane CLI commands and a clear, validated connection workflow. It loses points for an unnecessary Dropbox-overview paragraph and minor structural inconsistencies in step numbering.

Suggestions

Remove or trim the opening "Dropbox is a file hosting service..." paragraph, which explains concepts Claude already knows.

Fix step numbering inconsistency: label the connection steps clearly (1a/1b → Step 2) so the referenced "Step 2" is unambiguous.

Consider moving the popular-actions table and full clientAction state details into a separate reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The intro paragraph explaining what Dropbox is ("a file hosting service that provides cloud storage, file synchronization...") is content Claude already knows and is padding, matching the 3-anchor ("Mostly efficient but includes some unnecessary explanation"); not a 2 because the rest is mostly lean command-driven guidance.	3 / 5
Actionability	It provides copy-paste-ready executable commands for install, auth, connection, polling, action search/run, and proxy requests plus a flags table, covering the common cases per the 5-anchor ("Fully executable; copy-paste ready code or commands").	5 / 5
Workflow Clarity	A clear connect → poll → search → run sequence exists with state-driven checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a retry-after-action loop, fitting the 4-anchor; not a 5 because step numbering is inconsistent (a "1b" with no labeled Step 1/Step 2, and references to an unlabeled "Step 2").	4 / 5
Progressive Disclosure	Single self-contained file with well-organized section headers and no nested references, fitting the 4-anchor ("Good structure; most content is appropriately placed"); not a 5 because the 15-row popular actions table and detailed clientAction state handling are inlined content that could live in separate reference files.	4 / 5
	Total	16 / 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 names the Dropbox domain and a single action with an explicit Use-when clause, so both what and when are present. It is held back by minimal action coverage and a generic trigger phrase that misses common Dropbox terms.

Suggestions

Expand the action list beyond "Manage Accounts" to concrete operations (e.g., list/search files and folders, create/move/delete, manage shared links) to raise specificity.

Add natural trigger keywords users actually say — files, folders, shared links, storage, sync — to improve trigger term coverage.

Make the "when" clause more specific, e.g. "Use when the user wants to manage Dropbox files, folders, or shared links."

Dimension	Reasoning	Score
Specificity	"Manage Accounts" names the Dropbox domain plus one concrete action, matching the 3-anchor ("Names domain and 1-2 concrete actions, but not comprehensive"); it is not a 2 because a real action is named, and not a 4 because coverage is minimal with no other actions enumerated.	3 / 5
Completeness	It states the "what" ("Dropbox integration. Manage Accounts.") and an explicit "when" ("Use when the user wants to interact with Dropbox data"), matching the 4-anchor where both are present but the "when" could be more specific; not a 5 because the trigger is generic and lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural terms like "Dropbox" and "interact with Dropbox data" appear, but common synonyms users would say (files, folders, storage, sharing, sync) are missing, fitting the 3-anchor for partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	Dropbox is a named branded service giving a clear niche with low conflict risk, fitting the 4-anchor ("Mostly distinct; minor overlap risk"); not a 5 because "Manage Accounts" / "interact with Dropbox data" is somewhat generic and could overlap with a broader storage skill.	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/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.