dropbox-automation
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:Lingjie-chen/MT5 --skill dropbox-automation72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 explicit platform naming. However, it critically lacks a 'Use when...' clause that would help Claude know when to select this skill, and could benefit from more natural trigger terms users might actually say when needing Dropbox help.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Dropbox, cloud storage, sharing files via link, or syncing documents'
Include additional natural trigger terms users might say: 'cloud storage', 'share a link', 'sync files', 'Dropbox folder'
| 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 operational guidance, not usage triggers. | 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 'cloud storage', 'sync files', or 'share link'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to 'Dropbox' and 'Rube MCP (Composio)' which creates a distinct niche. Unlikely to conflict with generic file skills or other cloud storage integrations. | 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. The workflow sequences with explicit tool ordering and prerequisite markers are excellent, and the pitfalls documentation prevents common errors. The main weakness is verbosity - pitfalls are documented both inline and in a separate section, and the document could benefit from splitting detailed reference material into separate files.
Suggestions
Consolidate pitfalls into a single section or inline-only to reduce redundancy
Consider moving the Quick Reference table and Common Patterns to a separate REFERENCE.md file to reduce main skill length
| 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]/[Prerequisite] markers. Includes explicit validation steps (e.g., 'Confirm file exists with GET_METADATA before creating links') and async polling requirements for batch operations. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one large file. The 'Common Patterns' and 'Known Pitfalls' sections could be separate reference files. The quick reference table at the end is good but the overall document is quite long (~300 lines). | 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 | |
- 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.