Tessl • The management layer for AI agent skills

The body is highly actionable, with copy-paste-ready CLI commands and a strong connection-state polling workflow including error-state handling. Its main defects are a dangling reference to an undefined "Step 2", a padded intro explaining what Box is, a redundant "Popular actions" section, and no error-handling guidance for action execution results.

Suggestions

Remove the introductory paragraph explaining what Box is ("Box is a cloud-based content management and file sharing service... Dropbox or Google Drive") and the redundant "Popular actions" section that repeats the `action list` command already shown under "Searching for actions".

Fix the workflow sequence: define the steps explicitly (1. install, 2. authenticate, 3. connect, 4. discover actions, 5. run) so the reference "skip to **Step 2**" resolves to a real step, and add a brief note on interpreting error responses from `membrane action run`.

Trim or merge the headless-authentication and agent-type details (e.g. the trailing sentence "Those will be used to adjust tooling to be used best with your harness") into tighter guidance, and consider moving the proxy flag table into a small reference file to slim the main body.

Dimension	Reasoning	Score
Conciseness	The intro paragraph "Box is a cloud-based content management and file sharing service. It's used by businesses of all sizes... Think of it as a more business-focused alternative to Dropbox or Google Drive" explains a concept Claude already knows, and the "Popular actions" section merely repeats the `action list` command from the prior section. Mostly efficient elsewhere, but these are unnecessary explanations that could be trimmed — the 3 anchor, not 4's "minor instances".	3 / 5
Actionability	Commands are copy-paste ready and cover the common cases: `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://www.box.com/home" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json`, and a complete proxy flag table. This fully matches "fully executable; copy-paste ready code or commands; specific examples cover the common cases".	5 / 5
Workflow Clarity	The sequence (install → login → connect → discover → run → proxy) is only implicit in section order, and "If the returned connection has `state: "READY"`, skip to Step 2" references a Step 2 that is never defined in the document. Validation checkpoints exist for connection setup (poll `--wait`, handle `CLIENT_ACTION_REQUIRED` / `CONFIGURATION_ERROR`) but not for action-run outcomes, fitting "sequence present but checkpoints missing or implicit".	3 / 5
Progressive Disclosure	Good single-file structure with clear, logically ordered headers (Install the CLI, Authentication, Connecting to Box, Searching for actions, Running actions, Proxy requests, Best practices) and no bundle files; nothing at ~145 lines clearly demands splitting. Minor gaps — the redundant "Popular actions" section and the inlined proxy flag table — keep it at 4 rather than 5.	4 / 5
	Total	15 / 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 states both what the skill does (manage Box folders, users, groups, collaborations) and when to use it, in concise third-person voice with a distinctive domain name. Its main weaknesses are the generic verb "Manage", a slightly vague when-clause ("interact with Box data"), and missing natural trigger terms like "files" or "file sharing".

Dimension	Reasoning	Score
Specificity	"Manage Folders, Users, Groups, Collaborations" lists several concrete capability areas with only minor coverage gaps (files, uploads, sharing are absent). The single generic verb "Manage" applied to all objects keeps it below the 5 anchor's multiple specific action verbs, but it is broader than the 3 anchor's "1-2 concrete actions".	4 / 5
Completeness	Both parts are present: what ("Box integration. Manage Folders, Users, Groups, Collaborations.") and when ("Use when the user wants to interact with Box data."). The when-clause is explicit but generic ("interact with Box data"), fitting the 4 anchor ("'when' could be more explicit or specific") rather than 5's concrete trigger phrases.	4 / 5
Trigger Term Quality	Terms "Box", "Folders", "Users", "Groups", "Collaborations", and "Box data" are natural phrases users would say, but common variations like "files", "file sharing", or "content" are missing. This matches "good keyword coverage; a few natural terms missing" rather than the comprehensive synonym coverage of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Box" names a clear niche distinct from other storage/collab skills, but the word itself is polysemous and "Folders, Users, Groups, Collaborations" overlap with generic file-sharing skill language. This is "mostly distinct; minor overlap risk", short of 5's minimal conflict risk with distinct trigger phrases.	4 / 5
	Total	16 / 20 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: membranedev/application-skills
Path: skills/box/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

box

Table of Contents

Is this your skill?