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.
77
66%
Does it follow best practices?
Impact
97%
2.93xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/box-automation/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly enumerates specific Box cloud storage operations and uses natural trigger terms. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The operational instruction about searching tools first is useful but doesn't substitute for trigger guidance.
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.'
Consider adding file extension or URL triggers like '.box', 'box.com', or 'Box API' to further improve trigger matching.
| 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 specific operations, but lacks an explicit 'Use when...' clause. The instruction to 'always search tools first' is operational guidance, not a trigger condition. Per rubric, missing 'Use when' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Box', 'cloud storage', 'file upload', 'download', 'search', 'folder management', 'sharing', 'collaborations', 'metadata'. These cover common user language well. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to 'Box cloud storage' specifically, with the Rube MCP (Composio) integration detail. This is a distinct niche unlikely to conflict with other file or cloud storage skills targeting different platforms. | 3 / 3 |
Total | 11 / 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 competent API reference skill that covers Box operations comprehensively with clear tool sequences and useful pitfall documentation. Its main weaknesses are the lack of concrete executable examples (no actual MCP call demonstrations), significant content repetition across sections, and missing validation/error-recovery steps for destructive operations. The document would benefit from being more concise and including at least one end-to-end worked example.
Suggestions
Add at least 2-3 concrete MCP call examples showing actual tool invocations with sample parameters (e.g., a complete RUBE_SEARCH_TOOLS call followed by a BOX_UPLOAD_FILE call with real parameter values)
Consolidate repeated pitfalls (ID formats, pagination, nested parameters) into the 'Common Patterns' and 'Known Pitfalls' sections only, removing duplicates from individual workflow sections
Add explicit validation checkpoints to destructive workflows (delete folder/file): e.g., 'Verify folder contents with BOX_LIST_ITEMS_IN_FOLDER before deletion' and 'If error, check permissions with BOX_GET_FOLDER_INFORMATION'
Consider splitting the detailed parameter lists and quick reference table into a separate REFERENCE.md file, keeping SKILL.md as a leaner overview with the most common workflows
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but quite verbose for what it covers. There's significant repetition between sections (e.g., pitfalls about IDs being numeric strings appear in multiple places, pagination details repeated). The 'Known Pitfalls' section largely restates pitfalls already listed in individual workflows. The quick reference table is useful but adds length. Some parameter explanations are necessary since they're API-specific, but the overall document could be tightened by ~30%. | 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 sample parameters. The guidance is structured as reference documentation rather than copy-paste-ready instructions. A concrete example of an actual RUBE_SEARCH_TOOLS call or BOX_UPLOAD_FILE invocation with real parameter values would significantly improve actionability. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional), which is good. However, there are no explicit validation checkpoints or feedback loops. For destructive operations like BOX_DELETE_FOLDER and BOX_PERMANENTLY_REMOVE_FOLDER, there's no verify-before-proceeding step or error recovery guidance. The setup section has a reasonable sequence but the core workflows lack 'if this fails, do that' recovery patterns. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table. However, with no bundle files, this is a monolithic ~200-line document that could benefit from splitting detailed workflow sections or the full parameter reference into separate files. The single external link to Composio docs is appropriate, but the document tries to be both overview and complete reference simultaneously. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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 | |
d065ead
Table of Contents
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.