Name: dropbox-business
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

dropbox-business

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

Quality

66%

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-business/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 concrete, copy-paste-ready Membrane CLI commands and a well-sequenced connection workflow with state checkpoints. Its main weakness is conciseness — an opening paragraph explains a product Claude already knows — and it keeps all detail inline with no external references.

Suggestions

Trim or remove the opening paragraph explaining what Dropbox Business is; Claude already knows the product, so lead directly with how to use the skill.

Add an explicit validation step after running actions (e.g. inspect the `output` field for errors before proceeding), since actions and proxy requests can be destructive or batch.

Consider moving the detailed clientAction state handling and the proxy flag table into a separate reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient concrete CLI commands, but the opening paragraph ('Dropbox Business is a file hosting service operated by Dropbox that is tailored for businesses...') explains what Dropbox Business is — a concept Claude already knows — which is unnecessary padding, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands across the common cases — install, login, connection ensure/wait, action list/run with JSON input, and proxy requests with a full flag table — matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll loop, but the action-running and proxy steps lack explicit validation of results, fitting 'clear sequence with most checkpoints present; minor validation gaps' rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist and the body is a single file, but it is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices); some detailed inline content (clientAction state handling, the proxy flag table) could be split out, fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

57%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 uses third person and includes an explicit 'Use when' trigger, but its capabilities are generic ('manage data, records, automate workflows') rather than concrete Dropbox Business actions. Trigger coverage relies on repeating the product name without synonyms or natural variations.

Suggestions

Replace the generic verbs with concrete Dropbox Business capabilities, e.g. 'search and share files, manage team members and groups, handle file requests and legal holds'.

Broaden trigger terms with natural phrases and synonyms users actually say (e.g. 'Dropbox files, shared links, team folders, file requests') instead of repeating 'Dropbox Business'.

Make the 'when' clause scenario-specific, e.g. 'Use when the user wants to manage Dropbox Business files, team members, shared links, or automate Dropbox workflows'.

Dimension	Reasoning	Score
Specificity	It names the domain ('Dropbox Business integration') but the actions are minimal and generic — 'Manage data, records, and automate workflows' are abstract verbs with no concrete capabilities, matching the 'names the domain but actions are minimal or generic' anchor better than 3 since no concrete actions (e.g. share files, manage teams) are listed.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Dropbox Business data') are present, but the 'when' is generic and could be more specific, matching the 'has both what and when; when could be more explicit' anchor rather than 3 (where when is missing/weakly implied) or 5 (concrete trigger phrases).	4 / 5
Trigger Term Quality	The natural keyword 'Dropbox Business' is present and repeated in the trigger clause, but there are no synonyms, file extensions, or common variations (e.g. 'Dropbox files', 'shared links', 'team folders'), fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ('Dropbox Business') gives a clear niche with low conflict risk, but the generic action phrasing ('data, records, workflows') leaves minor overlap risk with adjacent file-storage/collaboration skills, so it fits 'mostly distinct; minor overlap risk' better than 5.	4 / 5
	Total	13 / 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-business/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.