CtrlK
BlogDocsLog inGet started
Tessl Logo

dropbox-automation

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

74

1.51x
Quality

63%

Does it follow best practices?

Impact

94%

1.51x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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.

The content is highly actionable with specific tool slugs and parameters and well-sequenced workflows, but it is held back by duplicated pitfall content, a missing validation checkpoint on destructive deletes, and a monolithic structure with no external references.

Suggestions

Add an explicit validation step before destructive/batch operations (e.g. call DROPBOX_GET_METADATA to confirm the path before DROPBOX_DELETE_FILE_OR_FOLDER) and a verify step after.

Remove the duplicated 'Known Pitfalls' section or fold it into the per-workflow Pitfalls blocks to eliminate redundancy.

Move the Quick Reference table and/or detailed pitfalls into a separate reference file and link to it from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient with specific tool slugs and parameters, but pitfalls are duplicated (per-workflow Pitfalls blocks and again in the 'Known Pitfalls' section) and async operations are listed twice, so it could be tightened.

3 / 5

Actionability

Provides concrete tool slugs, exact parameter names, valid enum values, and ordered sequences with [Required]/[Optional] tags; the minor gap is the absence of full example tool-call payloads.

4 / 5

Workflow Clarity

Workflows are clearly sequenced and batch ops include polling checkpoints, but the destructive delete workflow has no pre-delete validation step, so per the rubric guideline workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

Section structure is clear and well-organized, but the skill is monolithic (~230 lines) with no bundle files to offload the bulk Quick Reference table and duplicated pitfalls, and content that could be split remains inline.

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.

The description is specific and clearly niche-scoped to Dropbox via Rube MCP, with solid natural trigger terms. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

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

Replace the umbrella phrase 'file management' with more granular actions (e.g. 'create, move, rename, delete folders and files').

Include a few common synonyms users say (sync, backup, shared links) to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names several concrete actions ('sharing, search, uploads, downloads, and folder operations') plus the mechanism ('via Rube MCP (Composio)'), but 'file management' is umbrella-ish, leaving minor coverage gaps rather than fully granular actions.

4 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keywords a user would say (Dropbox, sharing, search, upload, download, folder), but missing common synonyms such as sync, backup, or links.

4 / 5

Distinctiveness Conflict Risk

'Dropbox ... via Rube MCP (Composio)' carves a clear, product-specific niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.