CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

box

Box manages cloud files, sharing, search, and metadata.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/productivity/box/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 body is an exemplary operational skill: lean imperative guidance, concrete commands and safety gates, explicitly sequenced task startup with thorough verification steps, and a clean overview-plus-routing-table structure backed by a complete one-level-deep reference bundle. Its only flaws are minor repetition across sections and deferring the exact CLI runner invocation to a reference.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and assumes Claude's competence — it never explains what Box, OAuth, or webhooks are. Minor redundancy keeps it from anchor 5: the "narrower access via an invited account" guidance appears twice (the "Start broad" and "Perform chosen setup" sections), and the same-computer-vs-remote-host question is repeated across three sections.

4 / 5

Actionability

Concrete, executable guidance throughout: `command -v box`, `Get-Command box -ErrorAction SilentlyContinue`, `box users:get me --json --fields id,name,login`, `box request`, the `ai:ask`/`ai:extract-structured`/`ai:extract`/`ai:text-gen` subcommands, and exact app.box.com URL patterns. Minor gap from anchor 5: the central "verified runner" invocation is deferred to cli-guide.md rather than shown, and several sections are policy statements whose specifics live in references.

4 / 5

Workflow Clarity

"Start each task" is a numbered, sequenced procedure with an explicit actor-validation checkpoint (`box users:get me --json`), and the "Verify" section mandates read-back after every write plus field-by-field comparison for metadata writes ("an HTTP success alone is not verification"), with discrepancy reporting and a smoke-folder create/verify/delete loop. Despite covering destructive and batch operations, validation checkpoints and the "Operate safely" checklist are explicit throughout, matching anchor 5.

5 / 5

Progressive Disclosure

SKILL.md is a genuine overview: the "Choose the right path" routing table maps each need to one of the ten reference files, every referenced path exists in references/, and all references are one level deep (sibling cross-links like search-and-ai.md → hubs.md are navigational, not buried content). No bulk reference material is inlined in the body, matching anchor 5's clear overview with well-signaled references.

5 / 5

Total

18

/

20

Passed

Description

53%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 concise and names a distinct product with several capability areas, but it reads as a domain label rather than an action list and provides no "Use when..." trigger guidance. It is serviceable for routing on the keyword "Box" but leaves the skill's activation conditions implicit.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user mentions Box, wants to upload/share/search cloud files, or asks about Box folders, Hubs, or file metadata."

Replace the generic verb "manages" with concrete actions: "Upload, organize, version, and share Box files; search content and metadata; run Box AI Q&A and extraction; build Box integrations."

Include natural synonyms and variations users would say ("Box folder", "file sharing link", "collaborate on documents") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"manages cloud files, sharing, search, and metadata" names the domain and several capability areas, but the only verb is the generic "manages" — the capabilities are bare nouns rather than concrete actions (no "upload", "share links", "extract metadata"). It sits between anchor 3 (1-2 concrete actions, not comprehensive) and anchor 4 (several specific actions with minor gaps); the generic single verb keeps it at 3.

3 / 5

Completeness

The description gives a clear "what" ("manages cloud files, sharing, search, and metadata") but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not anchor 2 because the "what" is concrete, not vague; not anchor 4 because the "when" is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Relevant keywords are present — "Box", "cloud files", "sharing", "search", "metadata" — but common natural variations users would say are missing ("Box folder", "upload to Box", "collaborate", "file sharing link"). This matches anchor 3 (some relevant keywords, missing common variations or synonyms) and falls short of anchor 4's good-but-incomplete coverage.

3 / 5

Distinctiveness Conflict Risk

"Box" names a specific product with a clear niche, making it mostly distinct with only minor overlap risk against closely related cloud-storage skills (e.g., google-workspace, listed as a related skill). Not anchor 5 because the trailing phrase "cloud files, sharing, search, and metadata" is generic phrasing that also describes competing cloud-drive skills, and no explicit triggers distinguish when Box (vs. another drive skill) applies.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/productivity/box/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.