Find documents and investigate access errors
Ask the assistant to find invoices in a specified Box folder or diagnose a 403 error. The Box skills guide tool selection, scoped searches, and checks of the acting user and permissions.
Overview
Box Agent Skills gives AI assistants task-specific instructions for content operations, integration development, and legal document workflows. It helps the assistant choose between Box MCP, the Box CLI, and application SDKs, then follow the guidance appropriate to the task.
Your assistant can select installed skills when their descriptions match your request, or you can name a skill explicitly. Installing the instructions does not authorize Box access: tasks involving live content also need a connection authenticated for the intended Box user.
- Access depends on your connection Available Box operations depend on user permissions, app scopes, administrator settings, and product entitlements.
- Legal decisions stay with people The legal workflows use your firm's checklists and templates to prepare facts for review; attorneys determine legal risk and make legal decisions.
Use Cases
Plan a resumable bulk update
For a large metadata update or folder reorganization, use the CLI and integration guidance to plan batches, track individual outcomes, and retry only work whose result is known.
Build or improve a Box integration
Add file uploads using your application's existing authentication and an official Box SDK, or review a sync worker for redundant API calls, pagination, and rate-limit handling. SDK guidance focuses on Python and TypeScript/Node.
Check a new client's intake documents
Compare an intake folder with your firm's required-document checklist, extract matter details, and prepare a factual summary for attorney review. Engagement letters need firm approval and a registered Doc Gen template; conflict and sanctions checks remain with the firm's screening systems.
Compare contracts and track renewal dates
Compare a contract with an approved template, prepare a cited variance report, and store confirmed review information as searchable Box metadata. The workflow also covers expiration searches; attorneys determine risk and materiality.
Prepare an M&A data room
Use your firm's folder plan and access matrix to organize deal documents, confirm external collaborators' access, and answer due-diligence questions with document citations. Permissions are checked before and after external access changes.
Components
Skills
This plugin's skills 9Showing all 9
Box operations
box
Choose Box tools, find task guidance, and diagnose authentication or access errors.
box-mcp
Set up Box MCP access, discover tools, and verify content operations.
box-cli
Run and verify Box CLI operations, including bulk jobs and partial-failure recovery.
Integration development
box-sdk-development
Build and debug Box SDK application code, especially in Python and TypeScript/Node.
box-integration-best-practices
Review Box integrations for unnecessary calls, resumable bulk work, and rate-limit handling.
Legal workflows
The intake, contract, and M&A workflows also use the box and box-legal-workflows foundation skills.
box-legal-workflows
Shared collaboration roles and human-review boundaries for the legal workflow skills.
box-legal-workflows-intake
Check intake completeness, extract matter details, and prepare approved engagement letters.
box-legal-workflows-contract
Compare contracts, prepare cited variance reports, and track expirations for attorney review.
box-legal-workflows-ma
Organize deal rooms, confirm access, and answer due-diligence questions with citations.
No matching results.
Install
Install the Box plugin for your tool, or choose the skills-only method where offered. Live Box access is authorized separately.
Claude Code
Add Box's marketplace, then install its box plugin as a whole.
- 01
Add the marketplace in a Claude Code session.
In Claude Code chat/plugin marketplace add box/skills - 02
Open the Box plugin's installation panel, choose user, project, or local scope, and complete installation.
In Claude Code chat/plugin install box@box-plugin-marketplace - 03
Check the installation summary. If it requests a reload, close the panel to apply it; otherwise the plugin is active immediately.
- 04
Confirm that box appears in the Installed tab of the plugin manager, and that typing / in chat lists its skills under the box name.
Connect Box for live content
Set up the live connection separately using Box's Claude Code setup. This requires a Box enterprise account with the MCP server enabled by an administrator.
- 01
Have a Box administrator open Integrations > Custom Box MCP Server in the Box Admin Console, then Configuration > Add Integration Credentials. Set Redirect URIs to
http://localhost:PORT/callbackusing your chosen callback port, check Access scopes, and save. Obtain the generated Client ID and Client Secret. - 02
Add the connection from a terminal. Replace
YOUR-CLIENT-IDwith the generated Client ID andPORTwith the callback port set in the Admin Console.In a terminalclaude mcp add-json box-mcp \ '{"type":"http","url":"https://mcp.box.com","oauth":{"clientId":"YOUR-CLIENT-ID","callbackPort":PORT}}' \ --client-secret - 03
Paste the Client Secret when prompted and press Enter to open the browser authorization flow. Sign in to the intended Box account and complete authorization.
- 04
Start Claude Code and check that box-mcp is listed and connected.
In Claude Code chat/mcp - 05
Ask the assistant to discover its Box tools and call
who_am_ito confirm the intended Box user.
This method installs selected skill instructions without the plugin's MCP server configuration. You need Node.js and npm; installation is project-scoped by default.
- 06
Run the installer from your project directory. If prompted to install the skills package, confirm it. Select Claude Code and the Box skills you want; select all nine for the complete skill set.
In a terminal, from your project directorynpx skills add box/skills - 07
If the installer created a top-level skills directory after your Claude Code session started, reload skills.
In the existing Claude Code session, if needed/reload-skills - 08
List available skills and confirm that the Box skills you selected appear.
In Claude Code chat/skills
For live Box tasks, set up the connection your task uses. See the Skills CLI guide for installation scope and Claude Code's skill guide for discovery and loading.
- 06
Use a Pro, Max, Ultra, Team, or Enterprise plan with Code execution and file creation turned on for skills. Open Customize > Plugins in Claude Desktop or claude.ai. Select Add > Add marketplace and enter https://github.com/box/skills.
- 07
Open box from the added marketplace and select Add. On a managed account, your organization's plugin policies may restrict which sources you can add.
- 08
Open Customize > Skills > Your skills and confirm that the plugin's Box skills appear. Turn on the skills you want to use.
Connect Box for live content
Connect Box separately using Box's Claude setup. A Box administrator must enable Claude under Integrations in the Box Admin Console and set its availability to Available to all users. On Team and Enterprise plans, an organization Owner may need to add the connector first.
- 06
In Claude's prompt window, select + > Connectors > Add connectors. Search for Box and enable the connector.
- 07
Connect Box and sign in with your own Box account. Under Customize > Connectors > Your connectors, confirm that Box has the status Connected.
- 08
In the conversation, select + > Connectors and turn on Box.
Box provides marketplace and manual installation methods for Cursor.
Installation method
- 06
Open Cursor's marketplace panel or Customize page, search for Box, and install the Box plugin at project or user level.
- 06
With Git installed, clone Box's repository into Cursor's local plugins directory.
In a terminalgit clone https://github.com/box/skills.git ~/.cursor/plugins/local/box
- 06
Restart Cursor or run Developer: Reload Window. In Agent chat, type / and search for a Box skill to confirm it is available.
For live content tasks, configure and authorize Box through Cursor's MCP settings using the Box platform setup guide. Ask the assistant to discover the available tools and call who_am_i to check the Box user. Installation methods come from Box's Cursor guide; Cursor's plugin documentation covers plugin management.
This installs selected skill instructions without the plugin's MCP server configuration. You need Node.js and npm; installation is project-scoped by default.
- 06
Run the installer from your project directory. Confirm installation of the skills package if prompted, select Cursor, and choose the Box skills you want. Select all nine for the complete skill set.
In a terminal, from your project directorynpx skills add box/skills - 07
Restart Cursor so it discovers the installed skills. In Agent chat, type / and search for the Box skills you selected.
For live Box tasks, set up the connection your task uses. The Skills CLI guide covers installation scope, and Cursor's skill guide covers discovery and invocation.
Use Codex CLI to add Box's marketplace and install its plugin. Plugins are also supported in the desktop app; the IDE extension supports standalone skills instead.
- 06
Add Box's marketplace. This command combines Codex's documented marketplace syntax with Box's repository; Codex supports its legacy Claude marketplace manifest.
In a terminalcodex plugin marketplace add box/skills - 07
Open the plugin browser, find box in box-plugin-marketplace, and install it.
In Codex CLI chat/plugins - 08
Start a new Codex session before using the bundled skills or tools. Open the plugin browser again to confirm Box is installed, and check the skills menu for its skills.
For live Box tasks, keep credentials in your client settings and authorize the Box connection. Ask the assistant to discover its tools and call who_am_i to confirm the intended user. Sources: Codex marketplace support and plugin installation and loading.
Install selected Box skills for Codex CLI, the desktop app, or the IDE extension. This method leaves out the plugin's MCP server configuration. You need Node.js and npm; installation is project-scoped by default.
- 06
Run the installer from your project directory. Confirm installation of the skills package if prompted, select Codex, and choose the Box skills you want. Select all nine for the complete skill set.
In a terminal, from your project directorynpx skills add box/skills - 07
Check the skills menu in Codex CLI or the IDE extension, or Skills in the desktop sidebar, for the Box skills you selected. Codex detects skill changes automatically; restart it if the new skills do not appear.
For live Box tasks, set up the connection your task uses. See the Skills CLI guide for scope and the Codex skill guide for availability checks.
- 06
In Kiro's Powers panel, find Box and install it. If it is not listed, choose Add Custom Power > Import power from GitHub, enter https://github.com/box/skills, and select Install.
- 07
Ask Kiro which skills are available in the current session and confirm that the Box skills appear. Kiro activates installed powers when a request relates to them.
Connecting to Box is separate from installing the Power. For a custom connection, a Box administrator creates Integration Credentials in the Admin Console with a Client ID, Client Secret, the client's redirect URI, and access scopes. Kiro's MCP OAuth settings take these credentials; the client-secret connection is documented for Kiro CLI only, because Kiro IDE supports public clients.
Neither vendor explains how to attach these credentials to the Power's bundled MCP server; consult the Box MCP setup guide and Kiro MCP configuration before connecting.
See Box's Kiro installation notes and Kiro's power installation guide.