Walks through client intake inside Box: checks whether submitted documents meet your firm's checklist, extracts client and matter details into searchable metadata, and generates the engagement letter once the firm approves.
WHEN TO USE
USE FOR
NOT FOR
This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.
PREREQUISITES:
- Use the
boxskill 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-workflowsskill 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
Do client intake in Box: inventory the intake folder, check completeness with Box AI against the firm's checklist, extract intake data into Box metadata, route via comments and collaborations, and generate the engagement letter with Box DocGen. This skill is the intake-specific recipe; the underlying Box tool mechanics live in the capability references below. The firm supplies the required-document checklist and risk criteria; conflict, PEP, and sanctions determinations run through the firm's screening system — not the agent or Box AI. Not legal advice.
Reach for these for tool mechanics rather than restating them here:
box skill's references/content-workflows.md — inventory the folder, metadata templates, set_file_metadata, file commentsbox skill's references/ai-and-retrieval.md — completeness checks and data extraction; pacing, limits, citationsbox skill's references/mcp-doc-gen.md — generate the engagement letter from a templatebox skill's references/collaboration.md — tag/route the attorney and share with the clientbox skill's references/mcp-search.md — find/inspect the firm's metadata templateRecord the intake outcome as file metadata so submissions stay searchable. Find or create the firm's template using the box skill's references/mcp-search.md and its references/content-workflows.md.
client_name, matter_name, practice_area, matter_owner, jurisdiction, matter_value, intake_status (complete/incomplete), risk_rating, assigned_attorney, decision, decision_date.| Intake task | Tool | Notes |
|---|---|---|
| Inventory submission | list_folder_content_by_folder_id | All files in the intake folder |
| Check completeness | ai_qa_multi_file | Present/complete/valid vs. firm checklist, with citations |
| Extract intake data | ai_extract_structured_from_fields_enhanced | Client, matter, jurisdiction, value |
| Write metadata | set_file_metadata | Record status, rating, decision, attorney |
| Tag attorney | create_file_comment | Route with the factual summary |
| Grant access | create_collaboration | Give the attorney access |
| Generate engagement letter | create_docgen_batch | Only if the firm approves |
| Share with client | add_folder_shared_link or create_collaboration | Confirm audience/expiration |
list_folder_content_by_folder_id. [CONFIRM: intake folder ID]ai_qa_multi_file — is each required doc (per the firm's checklist) present, complete, and valid, with citations? [CONFIRM: firm's required-document list]ai_extract_structured_from_fields_enhanced (client_name, matter_name, practice_area, jurisdiction, matter_value, …).ai_qa_multi_file to surface the facts the firm's criteria reference (value, jurisdiction, named parties) with citations. Do not use AI to determine conflicts, PEP status, or sanctions — pass names/entities/locations to the firm's screening system.set_file_metadata with the firm-confirmed risk_rating, intake_status, and decision.create_file_comment to tag the attorney with the factual summary; create_collaboration for access. [CONFIRM: who, access level]create_docgen_batch against the firm's template → output to the confirmed folder → share via create_collaboration or add_folder_shared_link. [CONFIRM: DocGen template, destination folder, share method/expiration]Box mechanics (DocGen template/tag requirements, external-sharing confirmation, AI pacing/limits/citations, metadata writes) are governed by the capability references above and box-legal-workflows. Specific to intake:
All items below are required.
Install the box skill first for 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 boxInstall the box-legal-workflows skill for the shared collaboration roles, Box AI boundaries, and confirmation phrasing this intake workflow reuses; run npx skills add box/skills --skill box-legal-workflows if it isn't already installed.
npx skills add box/skills --skill box-legal-workflowsThis 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.
This route installs the Box Agent Skills plugin package selected for your AI tool.
PLUGIN MARKETPLACE
Typed inside the agent's own prompt, not in a terminal. The marketplace is called box-plugin-marketplace, which is the part after the @.
/plugin marketplace add box/skills/plugin install box@box-plugin-marketplaceInstalling 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
Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.Installing to: for your intended tool. Stop if it names a different tool.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-intake" --full-depthAfter 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.
The repository is licensed under MIT — use, modification, and redistribution are allowed under that license’s terms.
View the repository’s license file on GitHub →