dropbox-automation

Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.

1.51x

Quality

70%

Does it follow best practices?

Impact

94%

1.51x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/dropbox-automation/SKILL.md

Quality

Content

57%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.

A well-structured, highly actionable MCP tool reference with concrete slugs, parameters, and pitfalls throughout. Its weaknesses are duplicated pitfall content, the lack of validation checkpoints around destructive and batch operations, and a monolithic single-file layout that inlines reference material that should be split out.

Suggestions

Add explicit validation steps to the delete/batch workflows (e.g., "Confirm with DROPBOX_GET_METADATA before DROPBOX_DELETE_FILE_OR_FOLDER" and a poll-then-verify loop for batch jobs).

Deduplicate the pitfalls: keep them once, either inline per workflow or in the "Known Pitfalls" section, not both.

Move the Quick Reference table and per-workflow parameter detail into a references/ file, keeping SKILL.md as a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of explanations of concepts Claude already knows, but pitfalls are duplicated between the workflow sections and the "Known Pitfalls" section (base64 encoding, 409 conflict, canonical path casing, path format rules, batch polling each appear twice), and the 23-row Quick Reference table restates every tool slug already listed in the workflows.	3 / 5
Actionability	Exact tool slugs, typed parameters with concrete examples (e.g., "options.file_categories", "2026-12-31T23:59:59Z"), and specific error codes give mostly executable guidance; gaps like how to obtain the s3key for the upload "content" object keep it from being fully copy-paste ready.	4 / 5
Workflow Clarity	Each workflow has a clear "When to use" and sequenced tool list, but the destructive/batch workflow (delete, batch move, batch delete) includes no validation or verification step — no metadata check before deletion and no verify-after feedback loop — which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Sections are clearly organized with consistent headers, but the ~230-line body inlines the full per-workflow API detail and a 23-row reference table that belong in separate reference files; no bundle files exist to offload this content.	3 / 5
	Total	13 / 20 Passed

Description

70%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.

A specific, well-scoped description that names concrete Dropbox actions and is clearly distinguishable from other skills. Its main weakness is the complete absence of "when to use" trigger guidance, and its keyword coverage misses several natural synonyms users might say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to upload, download, share, or organize files in Dropbox."

Include natural synonym phrasings such as "share link", "move/rename files", or "sync" to broaden trigger-term coverage.

Replace the generic "file management" with the concrete operations it covers (e.g., create, move, copy, delete) for full specificity.

Dimension	Reasoning	Score
Specificity	"file management, sharing, search, uploads, downloads, and folder operations" lists several specific concrete actions covering the Dropbox domain comprehensively, but "file management" is a generic umbrella term, leaving minor gaps versus the comprehensive anchor.	4 / 5
Completeness	The description clearly answers "what" (automate Dropbox operations via Rube MCP) but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	"Dropbox", "sharing", "search", "uploads", "downloads", and "folder" are natural phrases users would say, giving good keyword coverage, though common variations like "share link", "move", "rename", or "sync" are missing.	4 / 5
Distinctiveness Conflict Risk	"via Rube MCP (Composio)" combined with Dropbox-specific operations establishes a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	16 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/dropbox-automation/SKILL.md
Commit: 10bfc43

Reviewed: 8 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.