A toolkit for developers to get the most out of the Box Platform using AI
Start reading — 2 minnpx skills add box/skills/plugin marketplace add box/skillsMIT7 stars3,934 wordsUpdated 8 September 2026
Agent Skills to help developers using AI agents work with Box. Whether you’re building Box integrations in code, working with Box content via MCP tools, configuring webhooks, or using Box AI retrieval — this plugin gives your assistant the context it needs to do it right.
The skills in this repo follow the Agent Skills (opens in a new tab) format and can also be installed as a plugin for platforms like Codex, Cursor (opens in a new tab), Claude (opens in a new tab), including Claude Code and Cowork, and Kiro (opens in a new tab).
npx skills add box/skillsCheck out the latest and full list of skills here (opens in a new tab).
This repo can also be installed as a plugin for supported platforms. MCP connection and OAuth setup vary by platform — see the setup guide for your platform below.
The root plugin.json and mcp.json follow the Agent Plugins v1.0.0 specification (opens in a new tab). The portable MCP configuration declares the Box MCP endpoint; authentication remains managed by each client. Do not add credentials to this repository’s root mcp.json; configure them only in your client’s settings.
| Platform | Setup guide |
|---|---|
| Codex | .codex-plugin/README.md (opens in a new tab) |
| Cursor | .cursor-plugin/README.md (opens in a new tab) |
| Claude Code | .claude-plugin/README.md (opens in a new tab) |
| Kiro | Install as a 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. The bundled skills work in both Kiro IDE and CLI.
Note that the Box MCP Server currently does not support Dynamic Client Registration, so credential-free Power authentication is not yet available in Kiro IDE. Kiro CLI users can configure Box OAuth client credentials in their user MCP settings; future managed OAuth integration or confidential-client OAuth support in the IDE can enable the bundled MCP connection there.
Try it with: Use the Box Power to add Box file upload to this app.
Skills are automatically available once installed. The agent will use them when relevant tasks are detected. Here are some example prompts:
Add Box file upload to my app
Create a shared link for this folder
Set up Box webhooks for new file events
Search my Box account for invoices
Use Box AI to classify documents
Wire webhooks to process new uploads
Debug 401 errors with my Box JWT auth
Fix webhook signature verification
The Box skill follows the Agent Skills Open Standard (opens in a new tab):
SKILL.md - Skill manifest with frontmatter, routing table, workflow steps, and guardrailsreferences/ - Individual reference files (auth, content workflows, MCP tool patterns, AI/retrieval, etc.)Preferred order for agent tooling is MCP first, Box CLI second, and direct REST only as a last-resort fallback.
# With Box CLI installed and authenticated:
box users:get me --json
box folders:items 0 --json --max-items 5
# Last-resort fallback (for sessions where MCP/CLI are unavailable):
export BOX_ACCESS_TOKEN="your-token"
curl -sS -H "Authorization: Bearer $BOX_ACCESS_TOKEN" -H "Accept: application/json" "https://api.box.com/2.0/folders/0"Skills follow the Agent Skills specification (opens in a new tab). The Box skill is a directory with a SKILL.md file containing YAML frontmatter and markdown instructions, plus a references/ directory for feature-specific deep dives.
MIT
main, last pushed 8 September 2026.SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Box, declaring 1 plugin. It is read for editorial metadata only — never as the skill index, which is always the repository tree./box/skills.md, and each skill at its own .md URL.