box
Box integration via Apideck's File Storage unified API — same methods work across every connector in File Storage, switch by changing `serviceId`. Use when the user wants to read, write, upload, or search files, folders, and drives in Box. Routes through Apideck with serviceId "box".
81
78%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./connectors/box/SKILL.mdQuality
Discovery
100%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 strong description that clearly identifies the specific service (Box), the integration mechanism (Apideck File Storage unified API), concrete actions (read, write, upload, search), and explicit trigger guidance. The description is concise, uses third person voice, and provides enough technical detail to distinguish it from similar file storage skills for other connectors.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, upload, or search files, folders, and drives in Box.' Also mentions the technical mechanism (Apideck's File Storage unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both what ('read, write, upload, or search files, folders, and drives in Box' via Apideck unified API) and when ('Use when the user wants to read, write, upload, or search files, folders, and drives in Box'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Box', 'files', 'folders', 'drives', 'upload', 'read', 'write', 'search'. Also includes technical terms like 'Apideck', 'serviceId', and 'File Storage' that help with precise matching. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifies 'Box' as the target service, 'Apideck' as the integration layer, and 'serviceId "box"' as the routing mechanism. This clearly distinguishes it from other file storage connectors or generic file skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured with strong progressive disclosure and clear cross-references, but it leans more toward describing the Apideck/Box integration architecture than providing actionable, task-oriented guidance. The portability message is repeated multiple times, consuming tokens without adding new information. The skill would benefit from more concrete examples of common Box operations (upload, download, folder creation) and a clearer decision workflow for coverage gaps.
Suggestions
Add 2-3 more executable examples for common Box operations (upload file, create folder, search) rather than repeating the portability message
Consolidate the portability explanation into a single brief mention — the intro, 'Portable across 5 connectors' section, and 'Sibling connectors' section all say the same thing
Present the coverage-check → unified API → proxy fallback as an explicit numbered workflow with decision points, rather than separate disconnected sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 5 File Storage connectors' section repeats the portability message already stated in the intro, and the marketing-style language ('compounding advantage') adds no actionable value. The 'When to use this skill' section also over-explains activation triggers Claude could infer. | 2 / 3 |
Actionability | The minimal TypeScript example is executable and the curl commands are concrete, but the skill mostly describes how Apideck works rather than providing actionable patterns for common Box operations (upload, download, search, create folder). It tells Claude about the API more than showing how to use it for real tasks. | 2 / 3 |
Workflow Clarity | There's an implicit workflow (check coverage → use unified API → fall back to proxy), but it's not presented as a clear sequence with validation checkpoints. The coverage verification step is mentioned but not integrated into a decision workflow with explicit branching logic for when operations are unsupported. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure — the skill provides a concise overview with well-signaled, one-level-deep references to SDK skills, best practices, connector coverage, and the OpenAPI spec. Navigation is clear and references are consistently formatted. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- 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.