Box adds four agent skills while keeping account access separate

Box’s [October 22 developer announcement](https://blog.box.com/building‑box‑explore‑four‑new‑box‑agent‑skills‑and‑help‑shape‑whats‑next) introduces four agent skills: Box CLI, Box MCP, Box SDK Development and Box Integration Best Practices. They package instructions and reference patterns for agents working on content operations or application integrations. The important setup boundary is explicit: installing a skill does not connect an agent to a Box account or grant additional access. Live operations still need an authenticated CLI, MCP connection or application client. A skill describes how to approach a task; the connected identity and its permissions determine what the agent can actually do. That gives developers two separate checks before assigning work: choose guidance that matches the execution path, then establish that the existing connection can perform the requested operation. The announcement describes intended workflows, rather than independent evidence that an agent will complete them correctly.

The [Box CLI skill](https://blog.box.com/building‑box‑explore‑four‑new‑box‑agent‑skills‑and‑help‑shape‑whats‑next) is for shell‑based work through the official command‑line tool. Box says it asks the agent to confirm the acting user, resolve names to Box IDs, check syntax and verify changes. Its bulk‑operation guidance includes recording outcomes and recovering from partial failures. Box MCP is for an assistant using Box’s hosted MCP server. Its instructions cover setup, tool discovery, content operations and troubleshooting. Box says available capabilities depend on the client, administrator settings, permissions and product entitlements. An absent tool therefore needs investigation within that connection, rather than an assumption that every client exposes the same operations. Box SDK Development covers application work using the official Python or TypeScript/Node SDKs. It directs the agent to inspect the installed version, current client setup, authentication and workload before handling details such as pagination, transfers, retries and logging. Integration Best Practices addresses repeatable jobs, including API request patterns, bulk processing, rate limits and interrupted work. It can complement the SDK skill for a service or the CLI skill for a batch task. The distinction is the layer being examined: application code, command execution, assistant tools or the operation of the integration over time.

[Box’s partial‑failure example](https://blog.box.com/building‑box‑explore‑four‑new‑box‑agent‑skills‑and‑help‑shape‑whats‑next) is a batch of file moves. Before retrying, the agent should establish which moves succeeded, then deal with the remaining work. Restarting an entire batch without that check risks acting again on work already completed. This is workflow guidance, not a claim that installing the skill supplies transaction guarantees. The post gives `npx skills add box/skills` for interactive selection and `npx skills add box/skills --skill box‑sdk‑development` as a specific installation example. It says the runtime must support the Agent Skills format and that platform bundles may contain different selections. OpenTools has not installed these skills or tested a live Box operation. For a first task, Box recommends a workflow the developer already understands and a stated completion condition. An upload, for example, should be checked against the intended destination folder. That makes the result inspectable: an agent’s explanation or a successful command response alone does not establish that the requested content operation reached the right place. *Photo: [Jeanjung212](https://commons.wikimedia.org/wiki/user:Jeanjung212) / [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:Box_HQ_Redwood_City,_California.jpg), [CC BY‑SA 4.0](https://creativecommons.org/licenses/by‑sa/4.0/). Box headquarters in Redwood City, California, March 10, 2017. Archive company context, not a depiction of the new skills or evidence of where they run. Display crop and downscale; image adaptations retain the same licence.*