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 is clearly distinguishable from other cloud storage skills. However, it lacks an explicit 'Use when...' clause that would help Claude know when to select this skill, and some trigger terms could be more natural. The implementation note about searching tools first is useful but doesn't serve the selection purpose.

Suggestions

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

Include common user-facing variations like 'Box.com', 'Box drive', 'share a Box link', or 'Box folder' 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 integration method (Rube MCP / Composio).	3 / 3
Completeness	Clearly answers 'what does this do' with a list of Box operations, but lacks an explicit 'Use when...' clause. The guidance 'Always search tools first for current schemas' is an implementation instruction, not a trigger condition. Per rubric, missing 'Use when' caps completeness at 2.	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', 'share a file', 'move files to Box', or 'Box API'. The term 'Rube MCP (Composio)' is technical jargon unlikely to be used by most users.	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.).	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 skill provides comprehensive coverage of Box operations via Rube MCP with well-structured workflow sequences and useful pitfall documentation. Its main weaknesses are verbosity with repeated information across sections, lack of concrete executable examples showing actual MCP tool calls, and missing validation/verification steps in workflows that include destructive operations like deletion.

Suggestions

Add at least one concrete example showing an actual MCP tool call with sample input parameters and expected response structure (e.g., a complete RUBE_SEARCH_TOOLS → BOX_UPLOAD_FILE sequence with real parameter values).

Consolidate repeated information — ID formats, pagination, and nested parameter conventions are each explained 2-3 times across different sections. Keep them only in 'Common Patterns' and reference that section from workflows.

Add explicit validation/verification steps to destructive workflows (delete folder, delete file): e.g., 'Verify folder contents with BOX_LIST_ITEMS_IN_FOLDER before deletion' and 'Confirm deletion succeeded by checking BOX_GET_FOLDER_INFORMATION returns 404'.

Trim the Quick Reference table to only include the most common operations, since it largely duplicates the detailed workflow sections above it.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-organized but quite verbose at ~250 lines. There's significant repetition between sections (e.g., ID formats explained in 'Common Patterns', 'Known Pitfalls', and individual workflow pitfalls; pagination explained multiple times). The Quick Reference table duplicates information already covered in each workflow section. Some pitfalls like 'Deletions fail without sufficient permissions; always handle error responses' are generic advice Claude already knows.	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 exact JSON payloads or tool invocations. The guidance is specific enough to follow but stops short of copy-paste ready examples — it describes what to call rather than showing exact calls with sample inputs/outputs.	2 / 3
Workflow Clarity	Workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional), which is strong. However, validation checkpoints are largely missing — there are no explicit 'verify the upload succeeded' or 'check the response for errors before proceeding' steps. For destructive operations like folder deletion, there's no feedback loop (verify contents → confirm → delete → verify deletion). The pitfall about handling error responses is mentioned but not integrated into the workflow steps.	2 / 3
Progressive Disclosure	The content is structured with clear sections and a logical progression from setup to workflows to reference. However, with no bundle files, all content is in a single monolithic file (~250 lines). The Common Patterns, Known Pitfalls, and Quick Reference sections could be separate reference files, and the individual workflow sections contain enough detail that they could benefit from being split out, with the main SKILL.md serving as a concise overview.	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: 74c7031

Reviewed: about 21 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.