CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dropbox

Browse, search, read, upload, and share the user's Dropbox — including team/shared folders — through their own Dropbox connection.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 lean, highly actionable operational guide: complete executable curl commands for every operation, a clearly sequenced workflow with approval checkpoints and explicit error-recovery loops, and almost no wasted tokens. The only structural improvement would be splitting auth troubleshooting and composio proxy details into a reference file.

DimensionReasoningScore

Conciseness

Nearly every token is non-obvious operational knowledge (vault token behavior, Dropbox-API-Path-Root, 400/401/409 semantics) with no explanation of concepts Claude already knows; only the auth fallback and DM-vs-channel paragraphs could be tightened slightly. It is not a 5 because those passages have mild padding, and not a 3 because there are no genuinely unnecessary explanations.

4 / 5

Actionability

Every mainline operation (get_current_account, list_folder, continue, search_v2, download, upload, create_shared_link, move_v2, delete_v2) has a complete copy-paste-ready curl command with real headers and clearly marked substitutions (ROOT_NAMESPACE_ID, CURSOR, id:FILE_ID). The one omitted command (search/continue_v2) is explicitly described as identical in shape to a shown command, so it is not a gap worth dropping to 4.

5 / 5

Workflow Clarity

The sequence is explicit ("First: pick the right namespace"), writes have an approval checkpoint ("Prepare the exact change... get approval before running it"), and error recovery is a genuine feedback loop (400 → fix command and retry; 401 → reconnect unless missing_scope; 409 → reuse the existing link; paginate with cursor before concluding a file doesn't exist). Destructive operations do have verification steps, so the workflow cap does not apply.

5 / 5

Progressive Disclosure

Sections are well-organized with no nested references and the composio details are correctly delegated to that skill, but the ~177-line body keeps auth troubleshooting and proxy details inline with no bundle files to split them into. It is not a 5 because a single monolithic file holding everything is not ideal structure for this length, and not a 3 because navigation is easy and nothing is buried.

4 / 5

Total

18

/

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, distinctive description with concrete verbs and natural Dropbox keywords, but it lacks any explicit "Use when..." trigger clause and omits a couple of capabilities (move/delete) the skill actually supports. Adding trigger guidance would lift it from good to excellent.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about their Dropbox files or folders — listing, searching, reading, uploading, or sharing them."

Mention the remaining write operations (move/rename and delete, noting deletion is recoverable) so the capability list is comprehensive.

Include a few more natural trigger terms such as "files", "download", and "folders" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Browse, search, read, upload, and share" lists five concrete actions spanning reads and writes, matching the several-specific-actions anchor; it falls short of anchor 5 only because the body also supports move/rename and delete, which the description omits.

4 / 5

Completeness

The "what" is clear and concrete, but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 4 because the "when" is entirely absent rather than merely implicit, and not a 2 because the "what" half is fully specified.

3 / 5

Trigger Term Quality

Natural terms like "Dropbox", "search", "upload", "share", and "team/shared folders" cover what users would actually say, but common variations such as "files" and "download" are missing, placing it at good-but-not-comprehensive keyword coverage.

4 / 5

Distinctiveness Conflict Risk

"the user's Dropbox — including team/shared folders — through their own Dropbox connection" carves out a clear niche with distinct triggers ("Dropbox", "shared folders"), with minimal overlap risk against other cloud-storage 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.

Validation — 15 / 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

yc-software/qm

Path

skills-seed/dropbox/SKILL.md

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.