mcpField
B
box-legal-workflows-ma

box-legal-workflows-ma

github.com/boxDocuments7106 installsUpdated 2w ago
Repository

About box-legal-workflows-ma

A Box deal-room skill for legal teams managing M&A diligence. It sets up folder structures, scopes and verifies access, and supports cited due-diligence answers with Box AI; attorneys decide deal risk and terms.

Key features

  1. 01Create M&A deal-room folder structures
  2. 02Scope access by role and folder
  3. 03Audit and verify collaboration permissions
  4. 04Search and answer diligence questions with Box AI
  5. 05Extract terms and record them in file metadata

Use cases

  1. 01Build a categorized M&A deal room
  2. 02Set tiered access for internal and external parties
  3. 03Classify submissions into the appropriate folders
  4. 04Find deal documents and prepare cited diligence answers

MCP support

It relies on the `box` skill for Box MCP authentication, tool selection, and core workflows, using related capability references to manage folders, collaboration access, search, and AI retrieval.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/box/skills --skill box-legal-workflows-ma

After installing, type/box-legal-workflows-main Claude Code to confirm it loaded.

Details

From the project README

M&A Deal Room Management

PREREQUISITES:

  • Use the box skill for Box MCP auth, tool selection, and base workflows. If it is not installed, run: npx skills add https://github.com/box/skills --skill box
  • Use the box-legal-workflows skill for Box collaboration role definitions, Box AI usage boundaries, and reusable confirmation phrasings. If it is not installed, run: npx skills add box/skills --skill box-legal-workflows

Build and run an M&A data room in Box: create the folder hierarchy, scope role-based access with Box collaborations, validate permissions before sharing, and answer due-diligence questions with Box AI plus citations. This skill is the deal-room-specific recipe; the underlying Box tool mechanics live in the capability references below. Deal risk, materiality, and terms are attorney calls. Not legal advice.

Box capability references

Reach for these for tool mechanics rather than restating them here:

  • The box skill's references/content-workflows.md — create the folder hierarchy, upload/copy, classify-and-file submissions
  • The box skill's references/collaboration.md — role-based access, shared links, permission audits (list_item_collaborations)
  • The box skill's references/mcp-search.md — locate documents, folder-scoped search
  • The box skill's references/ai-and-retrieval.md — due-diligence Q&A and term extraction with citations

Folder structure

Create the tree using the MCP tools in the box skill's references/content-workflows.md (top-down, parent before child; reuse the existing folder on a 409 name conflict). Confirm the firm's template first. Example numbered structure — numeric prefixes keep ordering consistent and segregate external submissions:

[Deal Name] M&A Deal Room/
├── 01 - Financial Statements/
├── 02 - Legal Documents/
├── 03 - HR & Employment/
├── 04 - Intellectual Property/
├── 05 - Commercial Contracts/
├── 06 - Real Estate & Assets/
├── 07 - IT & Cybersecurity/
└── 08 - External Submissions/

Access model

Scope access least-privilege and folder-specific rather than root (role capabilities and external-sharing confirmation rules are in the box skill's references/collaboration.md and the bundled box-legal-workflows skill). Example deal-room mapping (confirm with the user):

  • Internal: Deal Lead → Editor/Co-Owner on root; Finance → Viewer on Financial Statements; Legal → Editor on Legal Documents.
  • External: External Counsel → Uploader on their own folder; Auditors → Viewer on Financial Statements; Prospective Buyer → Viewer on a curated subset, not the full room.

Tool selection

Deal-room taskToolNotes
Create folderscreate_folderBatch the hierarchy, top-down
Add filesupload_file / copy_fileNew uploads or copy existing Box files
Grant accesscreate_collaborationConfirm first for any external party
Shared linkadd_folder_shared_linkConfirm audience/expiration
Audit/verify accesslist_item_collaborationsBefore and after external changes
Find docssearch_files_keywordScope with ancestor_folder_id
Due-diligence Q&Aai_qa_multi_fileCross-document; surface citations
Extract termsai_extract_structured_from_fields_enhancedPersist with set_file_metadata
Classify submissionsai_qa_single_fileThen copy_file into the right folder

Workflow

  1. Setup: create the folder tree → grant internal access with create_collaboration. [CONFIRM: structure, emails/roles]
  2. Populate: upload_file/copy_file; classify submissions with ai_qa_single_file, then copy_file into the right category folder.
  3. External access: list_item_collaborations (audit) → [CONFIRM: who, folders, permission, expiration] → create_collaboration or add_folder_shared_link → list_item_collaborations (verify).
  4. Due diligence: search_files_keyword (folder-scoped) → ai_qa_multi_file → present the answer with citations; ai_extract_structured_from_fields_enhanced for terms → set_file_metadata to persist.

Legal guardrails

Box mechanics (external-sharing confirmation, shared-link settings, AI pacing/limits/citations) are governed by the capability references above and box-legal-workflows. Specific to deal rooms:

  • Deal risk, materiality, and term interpretation are attorney calls, never the agent's.
  • Validate permissions with list_item_collaborations before and after external changes — a folder grant exposes everything inside it, including files added later.
  • Audit trail: record returned folder/file/collaboration IDs and write DD summaries back to Box.

Comments

Markdown supported