Box

**Judgment** Mature, well-documented Box integration via the Maton gateway that should work effectively for most Box file and collaboration workflows, assuming network access and a valid Maton API key are available. **What it does well** - Covers the core Box v2 surface for everyday use: files, folders, uploads/downloads, shared links, collaborations, search, events, trash, collections, and webhooks. - Hides the complexity of Box OAuth by using managed connections; the assistant only needs the MATON_API_KEY and optionally a Maton-Connection ID. - Documentation is detailed and practical, with Python/JS examples, pagination notes, and explicit error/status behavior. **Key risks / limitations** - **Credential & environment dependency:** Requires a valid MATON_API_KEY and preconfigured Box connection(s) in Maton; without these, calls will fail (400/401). - **Data and security considerations:** All traffic is proxied via Maton, so Box file operations depend on Maton’s infrastructure and security posture; not suitable where direct-to-Box connectivity is mandated. - **Destructive operations:** Recursive folder delete, file delete, and trash/purge endpoints are available and not guarded by extra safety rails; careful confirmation logic is needed before issuing such calls. - **Permission variability:** Some capabilities (e.g., certain webhooks, listing users) require enterprise-level Box permissions; behavior may differ across tenants and could lead to 403/4xx errors that must be handled. **Recommended scenarios** - Assistants that organize, tag, and maintain a user’s Box file system (folder creation, cleanup, renaming, and moving items). - Workflows that need to upload generated artifacts (reports, code, exports) into Box and later retrieve or share them via links. - Collaborative workflows where the assistant manages shared links and collaborator roles for project folders. - Search- and audit-style tasks that query Box content (via search/events/recent items) and feed results into further analysis or summarization. Use this skill whenever the task explicitly involves Box file storage and collaboration. For integrations with other third-party services, prefer the separate `api-gateway` skill as indicated by the author.

**Quick judgment** A solid, feature-rich Box integration via the Maton gateway, well-suited for agents that need to upload, download, share, and organize Box content on behalf of users. It exposes most commonly needed Box functionality with a straightforward HTTP interface and managed OAuth. **Key strengths** - Broad coverage of core Box operations: files, folders, collaborations, shared links, search, events, trash, collections, and webhooks. - Managed OAuth and connection management via Maton simplifies handling multiple Box accounts. - Good documentation with practical code samples and clear notes on pagination, error handling, and upload specifics. **Main risks / limitations** - Hard dependency on the external Maton gateway and a valid `MATON_API_KEY`; outages or changes on Maton’s side affect all operations. - Access to Box is powerful: misuse or leakage of the Maton API key could lead to large-scale data exposure or deletion in Box. - Some advanced Box features (e.g., specialized enterprise/admin endpoints, deep governance/retention features) are not documented and may require direct Box integration if needed. - Rate limiting (HTTP 429) and Box-side enterprise permission requirements (e.g., for some webhooks/admin actions) can constrain heavy or administrative use. **Recommended scenarios** Use this skill when an agent needs to: - Act as a Box file manager: create folders, move items, clean up trash, and maintain a structured workspace. - Automate content sharing: generate shared links, adjust permissions, and manage folder collaborations for project workflows. - Build assistant workflows that search and read Box documents, then summarize, cross-reference, or transform their contents. - Integrate Box activity into productivity flows (e.g., watch events/recent items to notify users of important file changes). Avoid or supplement with other approaches if you require extremely high availability independent of Maton, or need niche Box enterprise/governance features not exposed here.