dropbox-automation
Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.
75
65%
Does it follow best practices?
Impact
94%
1.51xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/dropbox-automation/SKILL.mdQuality
Discovery
67%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 is strong in specificity and distinctiveness, clearly identifying Dropbox as the target platform and listing concrete operations. However, it lacks an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The instruction to 'always search tools first for current schemas' is an implementation detail that doesn't aid skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Dropbox files, cloud storage on Dropbox, sharing Dropbox links, or managing Dropbox folders.'
Include natural user-facing trigger terms like 'cloud storage', 'share a link', 'Dropbox folder', or 'sync files' to improve matching against common user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: file management, sharing, search, uploads, downloads, and folder operations. Also specifies the platform (Dropbox) and tooling (Rube MCP/Composio). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Dropbox file management, sharing, etc.), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the listed capabilities, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'Dropbox', 'file management', 'sharing', 'search', 'uploads', 'downloads', and 'folder operations', but misses common user variations like 'cloud storage', 'sync files', 'share a link', or file extension mentions. The terms 'Rube MCP' and 'Composio' are implementation details rather than user-facing trigger terms. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Dropbox specifically, with the additional qualifier of Rube MCP (Composio), making it highly distinct and unlikely to conflict with generic file management or other cloud storage skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive Dropbox automation skill with excellent workflow clarity — clear tool sequences, prerequisite steps, validation checkpoints, and well-documented pitfalls. Its main weaknesses are the lack of concrete executable examples (no actual MCP call syntax or JSON payloads) and significant content repetition between per-workflow pitfalls and the consolidated Known Pitfalls section. The monolithic structure would benefit from splitting into overview + detailed reference files.
Suggestions
Add at least one concrete, executable MCP call example per workflow (e.g., actual RUBE_SEARCH_TOOLS invocation with parameters and expected response shape) to improve actionability.
Eliminate the duplicated 'Known Pitfalls' section — the per-workflow pitfalls already cover this information, or consolidate all pitfalls in one place only.
Consider splitting detailed per-workflow documentation into separate referenced files (e.g., SEARCH.md, SHARING.md) and keeping SKILL.md as a concise overview with the quick reference table and links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~250 lines) with significant repetition between the per-workflow 'Pitfalls' sections and the consolidated 'Known Pitfalls' section. The quick reference table duplicates information already covered in each workflow. However, it avoids explaining basic concepts Claude already knows and stays focused on tool-specific details. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear tool sequences for each workflow, which is good. However, there are no executable code/command examples — no actual MCP call syntax, no JSON payloads, no concrete invocation examples. Everything is described at the parameter-documentation level rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | Each workflow has a clearly numbered tool sequence with explicit annotations ([Required], [Optional], [Prerequisite]), validation steps (e.g., check metadata before creating links, poll batch job status), and error recovery guidance. The sharing workflow explicitly includes prerequisite validation steps to avoid 409 conflicts, and batch operations include polling requirements. | 3 / 3 |
Progressive Disclosure | The content is a monolithic file with no references to external files for detailed information. The quick reference table and common patterns sections provide some structural organization, but the 250+ lines of content could benefit from splitting detailed per-workflow documentation into separate files with the SKILL.md serving as an overview with links. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- 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.