Skills
Chapter 3 of 5
Build and manage M&A virtual data rooms with Box MCP — create secure due-diligence folder structures, scope role-based access for internal teams and external parties, validate…
2 minutes · 447 words · 7 sections
PREREQUISITES:
- Read
box:boxfor Box MCP auth, tool selection, base workflows. If missing, run:npx skills add https://github.com/box/box-for-ai --skill box- Read
box-legal-workflowsfor Box collaboration role definitions, Box AI usage boundaries, and reusable confirmation phrasings. If missing, run:npx skills add box/box-for-ai --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.
Reach for these for tool mechanics rather than restating them here:
box:references/content-workflows.md — create the folder hierarchy, upload/copy, classify-and-file submissionsbox:references/collaboration.md — role-based access, shared links, permission audits (list_item_collaborations)box:references/mcp-search.md — locate documents, folder-scoped searchbox:references/ai-and-retrieval.md — due-diligence Q&A and term extraction with citationsCreate the tree using the MCP tools in box: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/Scope access least-privilege and folder-specific rather than root (role capabilities and external-sharing confirmation rules are in box:references/collaboration.md and box-legal-workflows). Example deal-room mapping (confirm with the user):
| Deal-room task | Tool | Notes |
|---|---|---|
| Create folders | create_folder | Batch the hierarchy, top-down |
| Add files | upload_file / copy_file | New uploads or copy existing Box files |
| Grant access | create_collaboration | Confirm first for any external party |
| Shared link | add_folder_shared_link | Confirm audience/expiration |
| Audit/verify access | list_item_collaborations | Before and after external changes |
| Find docs | search_files_keyword | Scope with ancestor_folder_id |
| Due-diligence Q&A | ai_qa_multi_file | Cross-document; surface citations |
| Extract terms | ai_extract_structured_from_fields_enhanced | Persist with set_file_metadata |
| Classify submissions | ai_qa_single_file | Then copy_file into the right folder |
create_collaboration. [CONFIRM: structure, emails/roles]upload_file/copy_file; classify submissions with ai_qa_single_file, then copy_file into the right category folder.list_item_collaborations (audit) → [CONFIRM: who, folders, permission, expiration] → create_collaboration or add_folder_shared_link → list_item_collaborations (verify).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.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:
list_item_collaborations before and after external changes — a folder grant exposes everything inside it, including files added later.Install this repository
npx skills add box/box-for-ai/plugin marketplace add box/box-for-aiSkills install per repository, not per chapter — the CLI has no documented per-skill form, so we do not print one.
Build and manage M&A virtual data rooms with Box MCP — create secure due-diligence folder structures, scope role-based access for internal teams and external parties, validate permissions before sharing, and answer cross-document due-diligence questions with Box AI. Use this skill when the user mentions M&A, deal rooms, data rooms, VDRs, due diligence, or mergers and acquisitions.
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
main, last pushed 7 August 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/box-for-ai.md, and each chapter at its own .md URL.