Box Agent Skills

Box Agent Skills

Agent Skills help AI assistants work with Box: find and organize content, support legal document workflows, and build or troubleshoot Box integrations. Each skill provides instructions for a specific kind of task, from client intake to SDK development and bulk operations.

The skills follow the Agent Skills format and can be installed individually or through a platform plugin. Installing instructions does not connect your assistant to Box; authorize Box access separately when your task needs it.

Available Skills

For application code, use box-sdk-development; for command-line work, use box-cli; for operations through a Box MCP connection, use box-mcp. Pair integration work with box-integration-best-practices when efficiency, bulk processing, or throttling matters.

The intake, contract, and M&A skills require both box and box-legal-workflows. The shared legal skill supports those workflows. Firms supply the checklists, templates, and review criteria; attorneys make legal and risk determinations.

Installation

Install individual skills

Choose skills interactively:

npx skills add box/skills

To install a specific skill, use its name from the catalog:

npx skills add box/skills --skill box-sdk-development

For a legal workflow, also install its required foundation skills. For example:

npx skills add box/skills --skill box
npx skills add box/skills --skill box-legal-workflows
npx skills add box/skills --skill box-legal-workflows-contract

Browse the Box skills listing for installation options.

Install a platform plugin

This repository also includes plugin configuration for supported platforms. Use the platform notes below, and follow the Box MCP supported-platform guides to connect and authorize Box access. Some repository notes describe plugin metadata rather than a complete installation flow.

For Box connection instructions for other clients, including Claude Cowork, see the supported-platform guides above.

The root plugin.json and mcp.json follow the Agent Plugins specification. The MCP configuration declares https://mcp.box.com; your client manages authentication. Store credentials in your client's settings, outside this repository.

Kiro Power

In Kiro, open the Powers panel and install the Box Power. If it is not shown in the catalog, select Add Custom Power → Import power from GitHub and enter https://github.com/box/skills.

Kiro is not listed in the Box MCP supported-platform guides. For a custom connection, follow the Box MCP setup guide and your Kiro client's MCP configuration instructions. Confirm that the client supports the required authentication flow. Installing the Power and authorizing a Box connection are separate steps.

Prerequisites

Requirements depend on the task:

Usage

Your agent uses installed skills when their descriptions match the task. You can name a skill explicitly when you want a particular workflow. Try these prompts, replacing folder references and firm materials with your own:

Verify Your Connection

Verify access through the tool you intend to use. A successful CLI or REST request does not verify your MCP connection or application SDK configuration.

• MCP: Ask your agent to discover the available tools and call who_am_i to confirm the intended Box user. Missing tools may require a client or administrator configuration change.
• CLI: Run the commands below to confirm the acting user and list a few root-folder items.
• SDK: Check the installed SDK version and use the application's configured client to make a small read request, such as retrieving the current user.

box users:get me --json
box folders:items 0 --json --max-items 5

For MCP tasks, perform operations and verification through the same connection. For explicit CLI tasks, use the CLI. For tasks without a specified tool, the box skill guides tool selection; direct REST requires an approved fallback and separate authentication.

curl -sS -H "Authorization: Bearer $BOX_ACCESS_TOKEN" \
  -H "Accept: application/json" \
  "https://api.box.com/2.0/users/me"

Skill Structure

Each skill lives in skills/<skill-name>/:

• SKILL.md — Required manifest with a name, description, and task instructions.
• references/ — Optional detailed guidance, such as SDK-specific instructions or Box capability references.

The box-cli, box-mcp, and box-integration-best-practices skills keep their instructions in a single SKILL.md. Other skills use references or guidance from related skills as needed. CLI syntax comes from installed command help; MCP tool names and inputs come from runtime discovery; SDK methods must match the installed SDK version.

Contributing

Follow the Agent Skills specification. Add or update a skill under skills/, with only the supporting resources its workflow requires. State any dependencies on other skills.

When adding or renaming a skill, update this README's catalog and example prompts, and review prerequisites and platform notes for affected guidance.

License

MIT

Privacy and Support

• Box Privacy Policy
• Box Support
• Repository issues for problems with these skill instructions.