Automate Dropbox file management, sharing, search, uploads, downloads, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill dropbox-automation74
Quality
63%
Does it follow best practices?
Impact
94%
1.51xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/dropbox-automation/SKILL.mdDiscovery
50%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 effectively lists specific Dropbox operations and is clearly distinguishable due to platform-specific naming. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill. The implementation note about searching tools first is internal guidance rather than selection criteria.
Suggestions
Add a 'Use when...' clause with trigger terms like 'when the user mentions Dropbox, cloud file sharing, or needs to sync/share files via Dropbox'
Include common user phrases like 'share a Dropbox link', 'sync to Dropbox', 'cloud storage' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'file management, sharing, search, uploads, downloads, and folder operations'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. The instruction to 'search tools first' is implementation detail, not usage guidance. | 1 / 3 |
Trigger Term Quality | Includes 'Dropbox', 'file management', 'sharing', 'search', 'uploads', 'downloads' which are relevant keywords, but missing common variations users might say like 'sync files', 'cloud storage', or 'share link'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Dropbox' and 'Rube MCP (Composio)' create a clear niche. This is unlikely to conflict with other file management skills due to the specific platform mention. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill for Dropbox automation with clear tool sequences, specific parameters, and good validation checkpoints. The main weakness is verbosity - pitfalls are documented both inline and in a separate section, and the quick reference table duplicates workflow information. The skill would benefit from consolidating redundant content or splitting detailed reference material into separate files.
Suggestions
Consolidate the 'Known Pitfalls' section with inline pitfalls to eliminate redundancy - either keep pitfalls only inline or only in the dedicated section
Consider moving the Quick Reference table to a separate REFERENCE.md file and linking to it, reducing the main skill length
Remove the 'Common Patterns' section content that duplicates information already covered in workflows (e.g., pagination is explained in each relevant workflow)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - pitfalls are repeated across sections and in a dedicated 'Known Pitfalls' section. The quick reference table duplicates information already covered in workflows. Could be tightened by consolidating pitfalls. | 2 / 3 |
Actionability | Provides specific tool names, exact parameter names with examples, and clear tool sequences for each workflow. Parameters include concrete examples like path formats and ISO date strings. The quick reference table makes tool selection immediately actionable. | 3 / 3 |
Workflow Clarity | Each workflow has numbered tool sequences with clear [Required]/[Optional] markers, prerequisite steps, and explicit validation checkpoints (e.g., 'Confirm connection status shows ACTIVE', 'MUST continue to avoid silently missing matches'). Batch operations include polling requirements. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~300 lines) with no references to external files for detailed content. The 'Known Pitfalls' section largely duplicates pitfalls already listed in each workflow section, suggesting content could be better split. | 2 / 3 |
Total | 10 / 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 | |
Table of Contents
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.