box-legal-workflows

Shared ground rules for Box-based legal workflows: which access level fits a collaborator, what Box's AI is and isn't allowed to decide, and stock wording for checking with a human before acting.

WHEN TO USE

SCOPE

USE FOR

Decide which Box collaborator role, like editor or viewer, fits a person's part in a matter.
Work out whether a task belongs to Box's AI or needs an attorney's sign-off instead.
Get ready-made wording for confirming a permission change or a risk rating with a human first.

NOT FOR

Giving final legal advice or making the legal decision itself.
Deciding who gets access — a human still approves permissions.
Running client conflict checks; that stays with the firm's own conflict system.
Making privilege calls or shaping settlement strategy.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (5)

Shared Legal Concepts

PREREQUISITE: Use the box skill for Box MCP authentication, tool selection, and base workflows. If it is not installed, run: npx skills add https://github.com/box/skills --skill box

Shared building blocks used by the legal skills (M&A, Intake, Contract Review): Box collaboration role definitions, the boundaries of where Box AI must not be the decision-maker, and reusable confirmation phrasings. Risk frameworks, metadata fields, workflows, and decision-transparency requirements live in the individual legal skills.

Box capability references

Reach for these for the underlying Box tool mechanics rather than restating them here:

The box skill's references/collaboration.md — collaborator role capabilities, shared links, and external-sharing rules
The box skill's references/ai-and-retrieval.md — Box AI Q&A, extraction, and structured metadata tools, with pacing/limits/citations

Box Collaboration Roles

[CONFIRM: What permission level is appropriate?]

For the full breakdown of each Box collaborator role (Co-owner, Editor, Viewer Uploader, Previewer Uploader, Viewer, Previewer, Uploader) and the exact capabilities each grants, see the role matrix in the box skill's references/collaboration.md. Use that matrix to determine which role fits a given collaborator, then have the human confirm the choice before granting access.

Apply least privilege: default to the most restrictive role that still lets the collaborator do their job, prefer specific folders over root access, and set expiration dates on external collaborations.

Box AI Boundaries

Box AI informs; a human attorney decides. Do NOT use Box AI for:

Final legal advice or decisions (human attorney only)
Access-control decisions (human approves permissions)
Client conflict checks (use the firm's conflict system)
Privilege determinations (attorney judgment)
Settlement negotiations or strategy

Box AI is appropriate for informing humans — completeness checks, risk-factor flagging, metadata extraction, contract comparison, and due-diligence Q&A — always with citations surfaced and a human making the final call.

For details on the Box AI tools available and how to use them, see the box skill's references/ai-and-retrieval.md.

Common Confirmation Patterns

Reusable phrasings for the human-in-the-loop confirmations the legal skills require.

Risk Rating

"Here are the factors I found: [...], with citations from Box. Under your firm's criteria, which rating applies?" (The agent presents facts; the firm's criteria and attorney determine the rating.)

Permissions

"I'll grant [person] [role] access to [folder/file]. They can [permissions]. Proceed?"

Routing

"Based on [practice area/risk/type], I recommend routing to [attorney]. Correct, or assign to someone else?"

Document Completeness

"Firm requires: [list]. Found: [list]. Missing: [list]. Proceed with assessment?"

Metadata Template

"Do you have a Box metadata template for [type]? If yes, scope and template key?"

Thresholds

"What is your firm's threshold for [matter value/expiration alert/risk escalation]?"

External Sharing

"Before sharing with [external party], confirm: (1) Permission level? (2) Folders? (3) Expiration? (4) Link or collaboration?"

MCP connection required

1 FOR YOU

01
Install the box skill for Box authentication
Install the box skill first — it handles Box MCP authentication, tool selection, and base workflows; run npx skills add https://github.com/box/skills --skill box if it isn't already installed.
```
npx skills add https://github.com/box/skills --skill box
```

This skill ships inside the Box Agent Skills plugin.

Needs a Box account connected through Box's MCP server. Set that up first — this skill doesn't include it.

Install the whole plugin

This route installs the Box Agent Skills plugin package selected for your AI tool.

PLUGIN MARKETPLACE

Add the marketplace, then install the plugin

Typed inside the agent's own prompt, not in a terminal. The marketplace is called box-plugin-marketplace, which is the part after the @.

01
```
/plugin marketplace add box/skills
```

/plugin install box@box-plugin-marketplace

Open plugin page ↗

Install without the plugin (incomplete)

What's missing

Installing just this skill adds only its own folder. Its instructions also call for other plugin components, such as shared scripts, reference files or other skills, which aren't included. Installing the whole plugin avoids this gap.

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add box/box-for-ai --skill "box-legal-workflows" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

View on GitHub