CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dropbox

Browse, search, read, upload, and share the user's Dropbox — including team/shared folders — through per-user OAuth.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

96%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.

An exemplary operational skill: executable curl recipes for every operation, careful error-recovery guidance, and tight non-obvious detail throughout. The only structural question is whether error-handling and auth details should be split into a reference file.

Suggestions

Consider moving the 400/401 error triage into a references/ file (e.g. references/errors.md) to slim SKILL.md further, keeping only the most common cases inline.

Add a short line stating the supported scope (list/search/read/upload/share/move/delete) up front so readers see the full operation set without scanning all sections.

DimensionReasoningScore

Conciseness

The body is dense, operational, and free of padding — every section covers non-obvious gotchas (namespace header requirement, Dropbox-API-Arg convention, no Content-Type on get_current_account) rather than concepts Claude already knows; it fits the 'every token earns its place' anchor, with only a trivial parenthetical that could be trimmed.

5 / 5

Actionability

Every operation ships a complete, copy-paste-ready curl command with correct headers, JSON bodies, and clearly marked placeholders (ROOT_NAMESPACE_ID, id:FILE_ID), plus pagination and error-handling variants — fully executable with no gaps.

5 / 5

Workflow Clarity

The sequence is explicit (resolve namespace once → operate by id → writes require prior approval) with real checkpoints and feedback loops: 400 fix-and-retry guidance, 401 vs missing_scope triage, 409 shared-link reuse, and 'confirm with users/get_current_account before telling a user Dropbox is broken'.

5 / 5

Progressive Disclosure

The single file is well-sectioned with clear headers and everything at one level, but there are no bundle files at all; the inline error-handling and credential sections could plausibly live in a references/ file given the >50-line length, so it sits between the 4 and 5 anchors.

4 / 5

Total

19

/

20

Passed

Description

75%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, weakened only by the complete absence of any 'Use when...' trigger clause. Adding one sentence of trigger guidance would raise it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions Dropbox, their Dropbox files, or asks to find, share, or upload files in their Dropbox."

Add natural synonyms such as "files", "folders", or "cloud storage" alongside "Dropbox" to broaden trigger coverage.

Optionally mention move/delete/rename in the action list to fully cover the operations the skill body supports.

DimensionReasoningScore

Specificity

The description lists five concrete actions ("Browse, search, read, upload, and share") plus a scoping clause ("including team/shared folders"), matching the comprehensive-coverage anchor rather than the 4 anchor, which implies minor gaps in the action list.

5 / 5

Completeness

The "what" is clear (browse/search/read/upload/share Dropbox), but there is no "Use when..." clause or equivalent trigger guidance; the rubric explicitly caps completeness at 3 for this, and it is not a 4 because 'when' is entirely missing rather than just imprecise.

3 / 5

Trigger Term Quality

"Dropbox", "team/shared folders" are the natural terms users would say, giving good coverage, but synonyms like "files", "cloud storage", or "sync" are absent, so it falls short of the 5 anchor's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

"the user's Dropbox" carves out a clear niche with a distinct product-name trigger, so it is unlikely to fire for any other skill.

5 / 5

Total

17

/

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.