box-automation

Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for current schemas.

2.93x

Quality

71%

Does it follow best practices?

Impact

97%

2.93x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/box-automation/SKILL.md

Quality

Content

68%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 a well-structured, actionable reference for Box automation via Rube MCP with clear workflow sequencing and a useful quick-reference table. Its main gaps are missing validation/feedback loops around destructive and batch operations and some redundancy across sections.

Suggestions

Add explicit validation checkpoints for destructive/batch operations (e.g., verify folder contents/permissions before BOX_DELETE_FOLDER, confirm recursive:true intent, and re-check after permanent removal).

De-duplicate the ID-format and pagination material that appears in both 'Common Patterns' and 'Known Pitfalls', keeping each section focused.

Include at least one complete worked tool-call example (e.g., a full BOX_UPLOAD_FILE invocation with the attributes-before-file ordering) to lift actionability toward fully executable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with tight tool/parameter/pitfall lists that assume competence, but some redundancy between 'Common Patterns', 'Known Pitfalls', and the 'Quick Reference' table could be trimmed.	4 / 5
Actionability	Concrete tool slugs, specific parameters, and real values (root '0', parent__id, RFC3339 ranges) give mostly executable guidance; absence of literal code is acceptable for an MCP-tool skill, though no fully worked example call is shown.	4 / 5
Workflow Clarity	Tool sequences are clearly ordered with [Prerequisite]/[Required]/[Optional] tags and an auth-status checkpoint, but destructive/batch operations (delete/permanently-remove folder, bulk) lack explicit validate-then-proceed feedback loops, capping clarity at 3.	3 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear section headers and a navigation-friendly Quick Reference table; no nested references, though size and minor inter-section duplication keep it just short of ideal.	4 / 5
	Total	15 / 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.

The description is specific and distinctive, enumerating concrete Box operations and naming the integration path. Its main weakness is the absence of explicit 'when to use' trigger guidance, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when the user wants to upload, download, search, or share files in Box').

Include natural synonyms and file references a user might say (e.g., 'Box files', 'Box folders', 'Box documents').

Drop the procedural 'Always search tools first for current schemas' from the description and move it into the body's setup steps to keep the description a capability/trigger statement.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'file upload/download, search, folder management, sharing, collaborations, and metadata queries' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Has a clear 'what' with enumerated actions, but no 'Use when...' trigger clause; per guidelines a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Good keyword coverage with 'Box cloud storage', 'file upload/download', 'search', 'sharing', but missing natural synonyms and file extensions a user would say (e.g., 'Box files', '.box').	4 / 5
Distinctiveness Conflict Risk	'Box cloud storage ... via Rube MCP (Composio)' is a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/box-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

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.