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

58%

Does it follow best practices?

Impact

97%

2.93x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/box-automation/SKILL.md

Quality

Discovery

67%

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 does a good job listing specific Box operations and naming the integration platform, making it distinctive and specific. However, it lacks an explicit 'Use when...' clause that would help Claude know exactly when to select this skill, and some of the terminology (Rube MCP, Composio) is technical rather than user-facing. Adding trigger guidance and more natural user terms would strengthen it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Box, Box.com, or needs to manage files/folders in Box cloud storage.'

Include natural user-facing variations like 'Box.com', 'Box files', 'Box folders', 'cloud drive' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: file upload/download, search, folder management, sharing, collaborations, and metadata queries. Also specifies the platform (Box) and the integration method (Rube MCP/Composio).	3 / 3
Completeness	Clearly answers 'what does this do' with specific Box operations, but lacks an explicit 'Use when...' clause. The 'when' is only implied by the capabilities listed. The instruction to 'always search tools first' is operational guidance, not a trigger condition.	2 / 3
Trigger Term Quality	Includes good keywords like 'Box', 'cloud storage', 'file upload/download', 'sharing', 'collaborations', and 'metadata', but misses common user variations like 'Box.com', 'cloud files', 'shared folders', or 'file management'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to Box cloud storage specifically, with distinct triggers like 'Box', 'Composio', and 'Rube MCP'. Unlikely to conflict with skills for other cloud storage providers (Google Drive, Dropbox, etc.) or general file operations.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive Box automation skill that covers many workflows with specific tool names, parameters, and pitfalls. Its main weaknesses are verbosity with repeated information across sections, lack of concrete executable examples showing actual MCP tool invocations, and missing validation/verification checkpoints in destructive workflows. The content would benefit from being split across files and adding concrete call examples.

Suggestions

Add concrete, copy-paste-ready examples of actual MCP tool invocations (e.g., a complete RUBE_SEARCH_TOOLS call followed by a BOX_UPLOAD_FILE call with real parameter values) to improve actionability.

Remove the duplicated 'Known Pitfalls' section at the bottom since the same information is already covered in per-workflow pitfall subsections, or consolidate all pitfalls into one location only.

Add explicit validation checkpoints to destructive workflows (delete folder, permanent delete) such as 'Verify folder contents before deletion' and 'Confirm deletion succeeded by checking trash'.

Split detailed parameter references and the quick reference table into a separate REFERENCE.md file, keeping the main skill focused on workflow sequences and key patterns.

Dimension	Reasoning	Score
Conciseness	The skill is quite lengthy (~200+ lines) with significant repetition between sections. The 'Known Pitfalls' section at the bottom repeats information already stated in per-workflow pitfalls (e.g., ID formats, search requirements). The quick reference table is useful but adds bulk. Some parameter descriptions are thorough but could be tightened.	2 / 3
Actionability	The skill provides specific tool names, parameter names, and clear tool sequences, which is good. However, there are no executable code examples or concrete MCP call examples showing actual invocations with real parameters. The guidance is specific but remains at the 'description of what to call' level rather than 'copy-paste ready' examples.	2 / 3
Workflow Clarity	Workflows are well-sequenced with clear step ordering and labeled as [Prerequisite], [Required], [Optional]. However, validation/verification steps are largely missing — for destructive operations like folder deletion, there's no explicit 'confirm before proceeding' or error-handling feedback loop. The setup section has a good verification flow, but core workflows lack validation checkpoints.	2 / 3
Progressive Disclosure	The content is structured with clear sections and a quick reference table, but it's monolithic — all content is inline in one file with no references to separate detailed documents. The extensive parameter lists and pitfalls for each workflow could be split into separate reference files, with the main skill providing just the overview and tool sequences.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: e654fb3

Reviewed: 5 days 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.