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

—

Does it follow best practices?

Impact

97%

2.93x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The body is highly actionable with concrete tool slugs, parameter values, and pitfalls, and workflows are cleanly sequenced. It is held back by cross-section content duplication and by the absence of explicit validation checkpoints on destructive operations and any progressive disclosure into separate reference files.

Suggestions

Add explicit validation checkpoints to destructive workflows — e.g., before BOX_DELETE_FOLDER, call BOX_GET_FOLDER_INFORMATION to verify permissions and use if_match with the ETag — to raise workflow clarity to 3.

De-duplicate ID format, pagination, and nested-parameter notes by keeping them only in Common Patterns and removing the repeats from per-workflow pitfalls and Known Pitfalls.

Move the Quick Reference table and detailed per-workflow parameter lists into a references/ file (e.g., REFERENCE.md) and link from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly information-dense (tool sequences, params, pitfalls), but the same facts repeat across sections — root folder "0", double-underscore nesting, and pagination each appear in both per-workflow pitfalls and Common Patterns/Known Pitfalls — and could be tightened.	2 / 3
Actionability	Guidance is concrete and copy-paste ready: exact tool slugs, specific parameter values (parent_id "0", file extensions with no dots), concrete error codes (HTTP 400 metadata_after_file_contents), URL-to-ID extraction, and a Quick Reference table — actionable without code, which is acceptable for an instruction-only MCP skill.	3 / 3
Workflow Clarity	Each workflow is a clearly numbered, tagged ([Prerequisite]/[Required]/[Optional]) tool sequence, but destructive operations (folder deletion, permanently-remove, file delete) lack inline validation checkpoints (e.g., verify permissions or if_match ETag before deleting), which caps workflow clarity at 2 per the guidelines.	2 / 3
Progressive Disclosure	No bundle files exist and everything is inline in a ~230-line single file; sections are well-organized, but the Quick Reference table and per-workflow parameter details are reference material that could live in a separate file, matching the anchor where content that should be separate is inline.	2 / 3
	Total	9 / 12 Passed

Description

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 is specific and clearly Box-scoped, but it lacks an explicit "Use when..." trigger clause and mixes natural user terms with implementation jargon, capping completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when the user wants to upload, search, share, or manage files and folders in Box") to lift completeness to 3.

Soften jargon like "collaborations" and "metadata queries" with user-facing phrasings such as "sharing access" and "search by custom fields".

Drop or relocate the "Always search tools first for current schemas" implementation note from the description into the body, since it is not a capability or trigger.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "file upload/download, search, folder management, sharing, collaborations, and metadata queries" — each a specific operation rather than vague language.	3 / 3
Completeness	Clearly states what the skill does (the enumerated operations) but provides no "Use when..." clause or equivalent explicit trigger guidance, so the "when" is only implied — capped at 2 per the guidelines.	2 / 3
Trigger Term Quality	Natural terms like "Box cloud storage", "upload/download", "search", and "sharing" appear, but they sit alongside jargon ("collaborations", "metadata queries", "Rube MCP (Composio)") and omit common phrasings like "Box files" or "Box folders".	2 / 3
Distinctiveness Conflict Risk	"Box cloud storage operations ... via Rube MCP (Composio)" names a clear, single-vendor niche unlikely to overlap with or trigger for other skills.	3 / 3
	Total	10 / 12 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
Commit: 366e45b

Reviewed: 2 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.