box-legal-workflows-intake
Automate legal client intake and onboarding with Box MCP — review uploaded intake documents for completeness against firm requirements, assess risk levels based on client profile and document content (PEP status, conflicts, sanctions, litigation history), route incomplete or high-risk submissions to appropriate attorneys with context and risk summaries, extract structured metadata (client name, matter type, jurisdiction, value), and generate engagement letters from Box DocGen templates for approved low-risk clients. Use this skill when the user mentions client intake, client onboarding, new client review, intake documents, engagement letters, or needs to process prospective client submissions stored in Box.
What this skill does
# Client Intake & Onboarding > **PREREQUISITES:** > - Read `box:box` for 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-workflows` for risk frameworks, confidentiality, human-in-the-loop requirements, Box AI governance. If missing, ensure it's installed from the same skill package. Legal client intake determines if the firm can and should take on a prospective client. This skill automates completeness checks, risk assessment, intelligent routing, and engagement letter generation. **Core principles:** Completeness first, risk-based routing, transparent decisions, human oversight for high-risk. --- ## Completeness & Risk Framework ### Required Documents Checklist **[CONFIRM: What documents required for intake?]** **Typical:** - Client intake form (completed questionnaire) - Valid government ID (passport, driver's license) - Conflict check authorization - Source of funds documentation (certain practice areas) - Business entity documents (corporate: articles, operating agreement) **Optional/practice-specific:** - Financial statements (bankruptcy, tax) - Prior legal proceedings (litigation) - Contracts or agreements (transactional) **Validation questions:** 1. Document present? 2. Complete? (not blank, has expected info) 3. Valid? (ID not expired, forms signed, dates current) ### Risk Rating **[CONFIRM: Low/medium/high risk criteria for your firm?]** **See box-legal-workflows for:** General risk framework. **Low-risk:** Individual client, standard matter, no litigation, clear funds, all docs complete, no conflicts, value below threshold. **High-risk:** PEP, high-value, cross-border with sanctions, conflict identified, criminal with media, reputational risk. ### Routing Logic **[CONFIRM: How to route intakes?]** **Route based on:** 1. **Practice area**: Match matter to attorney expertise 2. **Risk level**: Low → associate, Medium → senior, High → partner 3. **Workload**: Current caseload if known 4. **Jurisdiction**: Attorney bar admission 5. **Language**: Attorney language capabilities **Example matrix:** | Risk | Route To | Action | |------|----------|--------| | Low | Auto-approve OR associate | Generate engagement letter (if allowed) | | Medium | Senior attorney | Add comment with risk summary | | High | Partner + Compliance | Detailed analysis, block auto-processing | | Incomplete | Intake coordinator | List missing documents | --- ## Tool Selection | Task | Primary Tool | Notes | |------|--------------|-------| | List intake folder | `list_folder_content_by_folder_id` | Get all submission files | | Review documents | `ai_qa_multi_file` | Completeness & validity | | Extract data | `ai_extract_structured_from_fields_enhanced` | Name, matter, dates | | Assess risk | `ai_qa_multi_file` | Multi-file risk analysis | | Create summary | `upload_file` | Write summary doc | | Write metadata | `set_file_metadata` | Record decision, risk, attorney | | Tag for review | `create_file_comment` | Tag attorney with instructions | | Grant access | `create_collaboration` | Give attorney access | | Generate letter | **[CONFIRM: DocGen?]** | Need template access | | Share with client | `add_folder_shared_link` OR `create_collaboration` | Provide client access | --- ## Implementation Workflow ### Phase 1: Intake Review 1. **Authenticate**: `who_am_i` 2. **[CONFIRM: Intake folder ID?]** 3. **Inventory**: `list_folder_content_by_folder_id` 4. **[CONFIRM: Map files to required checklist]** 5. **Assess completeness**: `ai_qa_multi_file` (questions for each doc) 6. **Extract info**: **[CONFIRM: Fields?]** → `ai_extract_structured_from_fields_enhanced` ### Phase 2: Risk Assessment 7. **Risk analysis**: `ai_qa_multi_file` (PEP, sanctions, conflicts, litigation, high value, inconsistencies) 8. **Assign rating**: **[CONFIRM: Match firm's criteria?]** ### Phase 3: Decision & Routing 9. **Determine action**: - **INCOMPLETE**: **[CONFIRM: Who follows up?]** - **HIGH RISK**: **[CONFIRM: Who reviews? Block auto-processing?]** - **MEDIUM RISK**: **[CONFIRM: Who based on practice area?]** - **LOW RISK**: **[CONFIRM: Auto-approve or needs review?]** 10. **Save summary**: `upload_file` (completeness, risk, factors, action) 11. **Write metadata**: **[CONFIRM: Template exists?]** → `set_file_metadata` ### Phase 4: Routing & Collaboration 12. **Add comment**: **[CONFIRM: Who to tag?]** → `create_file_comment` 13. **Grant access**: **[CONFIRM: Permission level?]** → `create_collaboration` ### Phase 5: Engagement Letter (If Low-Risk Auto-Approve) 14. **Generate letter**: **[CONFIRM: DocGen template ID?]** → Use DocGen if available 15. **Save**: `upload_file` 16. **Share**: **[CONFIRM: How? Expiration?]** → `create_collaboration` or `add_folder_shared_link` --- ## Guardrails **See box-legal-workflows for:** Human-in-the-loop requirements, confidentiality, Box AI governance. **Intake-specific:** **ALWAYS confirm before:** 1. Auto-approving any client (even low-risk) 2. Generating engagement letters without attorney review 3. Sharing engagement letters with clients 4. Assigning risk ratings 5. Routing to specific attorneys 6. Copying files to externally-accessible folders (if file was NOT already externally accessible) **CONFIRM if uncertain:** 7. Document completeness (if missing docs or validity is ambiguous) 8. Extracted metadata (if values are unclear or contradictory) **Proceed autonomously when confident:** - Writing metadata when extraction is clear and unambiguous - Copying/organizing intake files between folders (internal-only to internal-only, or external to external) - Creating intake summary reports - Extracting client information with high confidence - Assessing document completeness when criteria are clear **NEVER auto-approve without authorization:** - High-risk clients - Matters above value threshold - Clients in sanctioned jurisdictions - Matters with conflicts - Any category requiring human review per firm policy **Decision transparency:** - Document WHY (risk factors, missing docs) - Cite which documents reviewed - Record WHO decided (human or automated) - Timestamp - Make summary available to assigned attorney **Box AI usage:** - Pace 1-2 seconds apart - Context: "Assessing risk for law firm intake. Identify red flags..." - Surface specific passages supporting assessment - Human attorney must review final decision --- ## Example Workflows ### Example 1: Complete Low-Risk **Request:** "Review John Smith intake, ready to approve?" **Flow:** 1. **[CONFIRM]**: "Folder ID?" 2. `list_folder_content_by_folder_id` 3. Inventory: intake_form.pdf, drivers_license.jpg, conflict_check.pdf 4. **[CONFIRM]**: "Required: form, ID, conflict check. All present. Assess?" 5. `ai_qa_multi_file`: "Form complete? ID valid? Conflict check signed?" 6. `ai_extract_structured_from_fields_enhanced`: name, matter, value, jurisdiction 7. **[CONFIRM]**: "$5K estate planning - low-risk?" 8. **[CONFIRM]**: "Auto-approve or route to Sarah?" 9. Create summary, `set_file_metadata`, `create_file_comment`, `create_collaboration` 10. Report: "Docs complete, low-risk. Routed to Sarah." ### Example 2: Incomplete **Request:** "Review Acme Corp, what's missing?" **Flow:** 1. Get folder ID 2. `list_folder_content_by_folder_id` 3. Inventory: intake_form.pdf, business_license.pdf 4. **[CONFIRM]**: "Required: form, articles, operating agreement, officer ID, conflict check. Only have form and license. Confirm?" 5. `ai_qa_multi_file` verify 6. **[CONFIRM]**: "Missing: articles, agreement, ID, conflict check. Who follows up?" 7. Create summary, metadata, comment, collaboration 8. Report: "Incomplete. Missing 4 docs. Routed to Maria." ### Example 3: High-Risk **Request:** "Review International Trading LLC." **Flow:** 1. Get folder ID 2. `list_folder_content_by_folder_id` 3. **[CONFIRM]**: "Check PEP, sanctions, cross-border, high value?" 4. `ai_qa_multi_file`: "Red flag
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.