CtrlK
BlogDocsLog inGet started
Tessl Logo

box-automation

Automate Box operations including file upload/download, content search, folder management, collaboration, metadata queries, and sign requests through Composio's Box toolkit.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/box-automation/SKILL.md

The canonical home for this skill is box-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 highly actionable with concrete tool sequences and parameter guidance, but suffers from duplicated pitfall content and lacks validation checkpoints on its destructive/batch operations. With no bundle files, all reference material is inlined rather than progressively disclosed.

Suggestions

Add explicit validation checkpoints before destructive steps (e.g. 'Verify folder_id via BOX_GET_FOLDER_INFORMATION before BOX_DELETE_FOLDER; confirm recursive flag intent before setting it') to lift the workflow_clarity cap.

De-duplicate the 'Known Pitfalls' section against the per-workflow 'Pitfalls' blocks, or move one of them into a separate references file to remove the redundancy.

Split the large Quick Reference table and/or detailed parameter tables into a separate reference file (e.g. references/quick-reference.md) referenced one level deep from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient tool sequences and parameter lists, but the 'Known Pitfalls' section duplicates material already stated per-workflow (ID formats, root folder '0', pagination, URL ID extraction), adding avoidable tokens.

3 / 5

Actionability

Concrete tool slugs, specific parameter names and values (parent_id "0", offset max 10000, uppercase operators, double-underscore nesting), and a full quick-reference table; minor gap is the absence of any example showing an actual tool-call argument object.

4 / 5

Workflow Clarity

Workflows are clearly sequenced with [Prerequisite]/[Required]/[Optional] tags, but destructive and batch operations (delete/permanently-remove folder, delete file, zip download) lack explicit validate-before-act checkpoints, capping workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized with clear section headers, but at ~230 lines everything is inlined in SKILL.md with no bundle files; the quick-reference table and detailed pitfalls are reference material that would benefit from being split into separate files.

3 / 5

Total

13

/

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 clearly and specifically enumerates what the skill does across the Box toolkit, but omits any explicit 'when to use' trigger guidance, which caps completeness. It is distinctive and well-targeted.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user wants to upload or download files in Box, search Box content, manage Box folders, share Box files, or create Box Sign requests.'

Include natural synonyms and product phrasings users actually say (e.g. 'share a Box file', 'Box Sign', 'upload to Box') to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('file upload/download, content search, folder management, collaboration, metadata queries, and sign requests') with comprehensive coverage of the Box toolkit's surface area.

5 / 5

Completeness

Has a clear 'what' enumerating capabilities, but no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good natural-term coverage ('upload/download', 'content search', 'folder management', 'collaboration', 'sign requests') but missing common synonyms and Box-specific phrasings users would naturally say.

4 / 5

Distinctiveness Conflict Risk

Scoped explicitly to Box via Composio's Box toolkit with distinct, product-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.