client-intake

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/client-intake

Load
```
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md
```
→ practice areas, intake templates, supervision style, flag triggers.
Use the workflow below.
Route to practice-area template. Listen for cross-area issues throughout.
Conflict check flags. Triage classification.
Output formatted case summary with AI-assisted label, verification prompts, supervision routing.

/legal-clinic:client-intake

加载
```
~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md
```
→ 业务领域、接待模板、监督风格、标记触发条件。
使用以下工作流。
分配至对应业务领域模板。全程留意跨领域问题。
冲突检查标记。分类分级。
输出格式化案件摘要，包含AI辅助标签、验证提示、监督分配信息。

/legal-clinic:client-intake

Client Intake

客户接待

Purpose

目的

Intake is one of the biggest bottlenecks in clinics. A student might spend 45 minutes interviewing, another hour writing it up, more time spotting the issues. Meanwhile the waitlist grows.

This skill structures the conversation, produces the write-up, spots issues across practice areas, and flags conflicts — so the student's time goes to analysis, not transcription.

What it doesn't do: decide whether to take the case. That's the student's analysis and the professor's judgment. Claude accelerates the information-gathering and structuring, not the lawyering.

客户接待是诊所最大的瓶颈之一。学生可能要花45分钟进行访谈，再花1小时撰写记录，还要花更多时间识别问题。与此同时，等待名单还在不断变长。

本技能可规范对话流程、生成记录文档、识别跨业务领域问题并标记冲突——让学生能将时间用于分析而非转录。

**本技能不负责：**决定是否受理案件。这需要学生分析后由教授判断。Claude仅加速信息收集和结构化处理，不替代法律工作。

Load context

加载上下文

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

→ practice areas, intake templates (per practice area if multiple), supervision style, jurisdiction, flag triggers.

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

→ 业务领域、接待模板（若有多个则按业务领域划分）、监督风格、管辖区域、标记触发条件。

Read the supervisor guide

阅读主管指南

Check for a practice-area guide at

~/.claude/plugins/config/claude-for-legal/legal-clinic/guides/<practice-area>.md

. If one exists, use its intake questions, red flags, and good-fit criteria instead of the generic defaults below. If one doesn't exist, use the generic intake and note at the end of the intake summary: "This was a generic intake — your supervisor can tailor the questions for your clinic type with

/legal-clinic:build-guide

When the intake starts before the practice area is routed (Step 1 of the workflow below), re-check for the guide after routing — the guide path depends on which practice area the intake landed in.

查看

~/.claude/plugins/config/claude-for-legal/legal-clinic/guides/<practice-area>.md

路径下的业务领域指南。若存在该指南，则使用其中的接待问题、警示信号和适配标准，而非下文的通用默认内容。若不存在，则使用通用接待流程，并在接待摘要末尾注明：“本次为通用接待流程——你的主管可通过

/legal-clinic:build-guide

为你的诊所类型定制问题。”

若在业务领域分配前就启动了接待（即下文工作流的步骤1），则在分配业务领域后重新检查指南——指南路径取决于接待所属的业务领域。

Workflow

工作流

Step 1: Practice area routing

步骤1：业务领域分配

Which practice area does this intake start in? The client may not know — they know their problem, not the legal category.

"Tell me what's going on — what brought you to the clinic today?"

From the answer, route to the appropriate intake template. If the clinic handles multiple areas and the problem spans them (housing client mentions immigration status, family client mentions domestic violence), note all relevant areas — cross-area issue spotting is a feature, not a bug.

本次接待属于哪个业务领域？客户可能并不清楚——他们只知道自己的问题，不知道对应的法律类别。

“告诉我具体情况——你今天来诊所是因为什么问题？”

根据客户的回答，分配到对应的接待模板。若诊所处理多个业务领域，且客户问题涉及多个领域（比如住房客户提及移民身份，家庭客户提及家庭暴力），则记录所有相关领域——跨领域问题识别是本技能的特色，而非缺陷。

Step 2: Practice-area-specific intake

步骤2：特定业务领域的接待流程

Each practice area asks different questions. Use the template from

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

for this area. Defaults if none provided:

Immigration:

Current status and how entered
Any prior applications, removals, encounters with ICE/CBP
Country conditions relevant to any asylum/withholding claim
Family members and their statuses
Criminal history (sensitive — explain why asking)
Timeline urgency: any pending hearings, deadlines, NTAs

Housing:

Type of housing (private, subsidized, public)
What happened: notice received, lockout, conditions problem, deposit dispute
Lease terms and payment history
Habitability issues (repairs requested, landlord response, documentation)
Timeline urgency: notice date, court date if any

Family:

Relationship and what's at issue (custody, support, divorce, protection)
Children involved — ages, current arrangement
Safety: any violence, threats, fear (handle carefully — see cross-area flags)
Existing court orders
Timeline urgency: any hearings scheduled

Consumer:

Type of debt or dispute
Who's contacting them and how (FDCPA relevance)
Documentation: contracts, statements, collection letters
Has anything been filed against them
Timeline urgency: answer deadlines, garnishment, judgment

不同业务领域的问题不同。使用

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

中对应领域的模板。若未提供模板，则使用以下默认内容：

移民领域：

当前身份及入境方式
过往申请、递解出境记录、与ICE/CBP的接触经历
与庇护/拒绝递解申请相关的母国情况
家庭成员及其身份
犯罪记录（敏感内容——需说明询问原因）
时间紧迫性：是否有pending hearings、截止日期、NTA

住房领域：

住房类型（私人、补贴、公共）
事件详情：收到通知、被锁门、住房条件问题、押金纠纷
租赁条款及付款记录
宜居性问题（已申请维修、房东回应、相关证明）
时间紧迫性：通知日期、若有则注明开庭日期

家庭领域：

关系及争议点（监护权、抚养费、离婚、保护令）
涉及的儿童——年龄、当前安排
安全问题：是否有暴力、威胁、恐惧（需谨慎处理——参见跨领域标记）
现有法院命令
时间紧迫性：是否已安排听证会

消费者领域：

债务或纠纷类型
联系方及联系方式（与FDCPA相关）
相关文件：合同、账单、催收函
是否已被起诉
时间紧迫性：答辩截止日期、扣押财产、判决结果

Step 3: Cross-practice-area issue spotting

步骤3：跨业务领域问题识别

While running the practice-area template, listen for issues outside that area:

Client says	Also flags
"I'm worried about my immigration status"	Immigration issue — even in a housing intake
"My partner [threatening behavior]"	DV / family law / protective order — even in a consumer intake
"I can't work because of my injury"	Possible benefits/disability claim
"They're taking money from my paycheck"	Garnishment — consumer/employment overlap
"The landlord said he'd call ICE"	Housing + immigration + possible retaliation claim

Note every cross-area issue in the summary. The clinic may handle it, refer it, or both — that's the professor's call. The student should see it.

在执行特定业务领域模板时，留意该领域之外的问题：

客户表述	同时标记
“我担心我的移民身份”	移民问题——即使是在住房接待中
“我的伴侣[有威胁行为]”	家庭暴力/家庭法/保护令——即使是在消费者接待中
“我因受伤无法工作”	可能涉及福利/伤残索赔
“他们从我的工资里扣钱”	工资扣押——消费者/雇佣领域交叉问题
“房东说他会联系ICE”	住房+移民+可能的报复索赔

在摘要中记录所有跨领域问题。诊所可能会处理、转介或两者并行——这由教授决定。学生需要知晓这些问题。

Step 4: Conflict check flags

步骤4：冲突检查标记

Per whatever conflict-check process

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

describes. At minimum:

Opposing party name(s) — does the clinic represent or have represented them?
Related parties — anyone else the student or clinic might have a conflict with?
Positional conflicts — is this case asking for something that would hurt another clinic client?

Flag for professor review. Don't resolve the conflict — surface it.

按照

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

中描述的冲突检查流程执行。至少需检查：

对方当事人姓名——诊所是否曾代表或正在代表他们？
相关方——学生或诊所是否与其他人存在冲突？
立场冲突——本案诉求是否会损害诊所其他客户的利益？

标记出来供教授审核。不要自行解决冲突——只需将其提出。

Step 5: Triage classification

步骤5：分类分级

Not a case-acceptance decision — a triage input:

Classification	Means
Urgent	Deadline in days, safety issue, irreversible harm imminent
Time-sensitive	Deadline in weeks, harm ongoing but not immediately irreversible
Standard	No immediate deadline, can queue normally
May be out of scope	Issue is outside clinic's practice areas — flag for referral assessment

这并非案件受理决定——而是分类分级的输入：

分类	含义
紧急	截止日期在数日内、存在安全问题、即将发生不可挽回的损害
时间敏感	截止日期在数周内、损害持续但并非立即不可挽回
标准	无即时截止日期，可正常排队处理
可能超出范围	问题超出诊所业务领域——标记以便评估是否转介

Step 6: Supervision flag check

步骤6：监督标记检查

Per

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

supervision style and flag triggers. If formal queue or configurable flags are enabled, and a trigger is present (deadline mentioned, DV indicator, immigration status at issue, etc.), note the flag.

根据

~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md

中的监督风格和标记触发条件执行。若启用正式队列或可配置标记，且存在触发条件（提及截止日期、家庭暴力指标、移民身份问题等），则记录该标记。

Step 7: Deadline handoff — required deliverable

步骤7：截止日期交接——必填交付项

If the intake surfaces any timeline deadline (answer due, hearing, statute-of-limitations cutoff, cure period, filing window, notice window, ICE check-in, removal hearing, eviction court date, protective order renewal), emit a copy-paste-ready
/legal-clinic:deadlines --add ...
block as part of the intake output. This is a required deliverable, not a suggestion — the intake identifies deadlines, and the student shouldn't have to re-transcribe them into the deadline skill.

Format each deadline as a fenced code block the student can copy, with every field pre-populated from the intake:

/legal-clinic:deadlines --add
  case=[case slug or client-last-name-keyword]
  type=[response|hearing|statute-of-limitations|discovery|cure-period|filing-window|notice|other]
  description="[one-line description of what is due]"
  due=[VERIFY — student + supervisor compute from triggering event]
  source="[triggering event + statute/rule cite, e.g., 'UD complaint served 2026-05-04, CCP § 1167']"
  owner=[student name]
  warnings=[14,7,3,1]

Rules:

One block per deadline surfaced. Do not combine. Each one will route through the deadlines skill's pre-add duplicate check.
Leave the
```
due=
```
value as
```
[VERIFY — student + supervisor compute]
```
when the deadline is jurisdictional (response deadline, SOL, notice window under a specific rule). The deadlines skill will not compute for you; the student + supervisor do the math and update the entry.
When a date is given in the triggering document (a hearing date on a summons, an ICE check-in date, a renewal deadline on a protective order), put that date in
```
due=
```
. When the date is computed (count N days from triggering event), leave the
```
[VERIFY]
```
marker.
If no deadline is surfaced in the intake, omit this section — don't fabricate one.

若接待过程中发现任何时间截止日期（答辩期限、听证会、诉讼时效截止、补救期、提交窗口、通知期限、ICE报到、递解出境听证会、驱逐法庭日期、保护令续期），需在接待输出中生成可直接复制粘贴的
/legal-clinic:deadlines --add ...
代码块。这是必填交付项，而非建议——接待流程负责识别截止日期，学生无需将其重新转录到截止日期技能中。

将每个截止日期格式化为学生可复制的围栏代码块，所有字段均从接待流程中预填充：

/legal-clinic:deadlines --add
  case=[case slug or client-last-name-keyword]
  type=[response|hearing|statute-of-limitations|discovery|cure-period|filing-window|notice|other]
  description="[one-line description of what is due]"
  due=[VERIFY — student + supervisor compute from triggering event]
  source="[triggering event + statute/rule cite, e.g., 'UD complaint served 2026-05-04, CCP § 1167']"
  owner=[student name]
  warnings=[14,7,3,1]

规则：

每个识别出的截止日期对应一个代码块。不要合并。每个代码块都会通过截止日期技能的预添加重复检查。
当截止日期受管辖规则约束（答辩期限、诉讼时效、特定规则下的通知期限）时，将
```
due=
```
值留为
```
[VERIFY — student + supervisor compute]
```
。截止日期技能不会自行计算，需由学生和主管计算并更新条目。
当触发文件中给出具体日期（传票上的听证会日期、ICE报到日期、保护令续期截止日期），则将该日期填入
```
due=
```
。当日期需要计算（从触发事件起算N天），则保留
```
[VERIFY]
```
标记。
若接待过程中未发现截止日期，则省略此部分——不要编造。

Output

输出

markdown

undefined

markdown

undefined

Intake Summary: [Client name or ID]

接待摘要：[客户姓名或ID]

[AI-ASSISTED DRAFT — requires student analysis and attorney review]

Privilege and confidentiality. This summary is derived from client communications that may be privileged, confidential, or both. It inherits the source's privilege status. Distributing it beyond the privilege circle (including outside the clinic) can waive privilege. Keep it in the clinic's privileged file store, mark it appropriately, and make distribution decisions with your supervisor.

Date: [date] | Intake by: [student] | Practice area: [primary + any cross-area]

[AI辅助草稿——需学生分析和律师审核]

保密与特权。本摘要源自可能具有保密特权或机密性的客户沟通内容，继承源内容的特权状态。将其分发至特权圈之外（包括诊所外部）可能会导致特权丧失。请将其存放在诊所的特权文件存储库中，适当标记，并在主管指导下决定分发范围。

日期： [日期] | 接待人： [学生] | 业务领域： [主要领域 + 所有跨领域]

Bottom line

核心结论

[Take the case / Decline because X / Need more info on Y — next step is Z]

[受理案件 / 因X拒绝 / 需获取Y的更多信息 — 下一步是Z]

Client's situation (in their words)

客户情况（客户原话）

[The narrative the client gave, before legal categorization. This is the human story.]

[客户讲述的事件经过，未进行法律分类。这是客户的真实经历。]

Legal issues identified

识别出的法律问题

Every statutory, ordinance, regulatory, rule, or case citation in this section carries a provenance tag (see plugin CLAUDE.md
## Shared guardrails
for the tag vocabulary).
[user provided]
if the supervisor uploaded the text,
[statute / regulator site]
if you fetched it this session from an official source, a research-connector tag (
[CourtListener]
, etc.) if it came from a tool result in this conversation,
[model knowledge — verify]
otherwise. The default is
[model knowledge — verify]
. A supervising attorney who cannot verify a cite against a connector needs to see the tag to know what to check first.

本节中的每一项法规、条例、规章或案例引用均带有来源标签（参见插件CLAUDE.md中的
## 共享防护规则
获取标签词汇）。若为主管上传的文本则标记
[user provided]
，若为本会话从官方来源获取则标记
[statute / regulator site]
，若来自本会话中的工具结果则标记研究连接器标签（如
[CourtListener]
等），否则标记
[model knowledge — verify]
。默认标签为
[model knowledge — verify]
。无法通过连接器验证引用的主管律师可通过标签了解优先核查内容。

Primary ([practice area])

主要领域（[业务领域]）

[Issue 1]: [one line with any cite tagged, e.g., "RLTO §5-12-080
```
[model knowledge — verify]
```
"]
[Issue 2]: [one line]

[问题1]：[一行描述，附带引用标签，例如：“RLTO §5-12-080
```
[model knowledge — verify]
```
”]
[问题2]：[一行描述]

Cross-practice-area flags

跨业务领域标记

[Other area]: [what the client said that raised it] [UNCERTAIN: whether clinic handles this or refers — professor call]

[其他领域]：[客户提及的引发标记的内容] [不确定：诊所是否处理该问题或转介——由教授决定]

Key facts

关键事实

Fact	Source	Documentation
[fact]	[client statement / document provided]	[have it / need it]

事实	来源	证明文件
[事实]	[客户陈述 / 提供的文件]	[已持有 / 需获取]

Conflict check

冲突检查

Opposing party: [name(s)] Related parties: [any] Flag: [clear / needs conflict check against clinic database]

对方当事人： [姓名] 相关方： [如有] 标记： [无冲突 / 需对照诊所数据库进行冲突检查]

Triage

分类分级

Classification: [Urgent / Time-sensitive / Standard / May be out of scope] Driving deadline: [if any — date and what it is]

分类： [紧急 / 时间敏感 / 标准 / 可能超出范围] 驱动性截止日期： [如有——日期及具体内容]

Deadlines to log

需记录的截止日期

[One

/legal-clinic:deadlines --add ...

block per surfaced deadline — Step 7. If none, omit this section.]

[每个识别出的截止日期对应一个

/legal-clinic:deadlines --add ...

代码块——参见步骤7。若无则省略此部分。]

Jurisdictional notes

管辖注意事项

Every statute, ordinance, rule, or case citation in this section carries a provenance tag — same vocabulary as
## Legal issues identified
. Default
[model knowledge — verify]
. When no research connector is reachable for this session, record it in the Sources: line of the reviewer note (see plugin CLAUDE.md
## Outputs
) — do not emit a standalone banner.

[State-specific or local-rule-specific issues relevant to this case type, per CLAUDE.md jurisdiction, with each cite tagged]

*本节中的每一项法规、条例、规章或案例引用均带有来源标签——与

## 识别出的法律问题

使用相同词汇。默认标签为

[model knowledge — verify]

。若本会话无法访问研究连接器，则在审核员备注的**来源：*行中记录（参见插件CLAUDE.md中的
## 输出
）——不要单独显示提示横幅。

[与本案类型相关的州级或地方规则问题，根据CLAUDE.md中的管辖区域，每个引用均带有标签]

Supervision flags

监督标记

[If supervision style includes flags: which fired and why. If formal queue: "QUEUED for [professor]."]

[若监督风格包含标记：触发的标记及原因。若为正式队列：“已排入[教授]的队列。”]

Verification prompts for the student

学生验证提示

Before analysis, verify:

[Specific fact the intake relies on — confirm with client or documents]
[Deadline date — confirm from the actual notice/court document, not client's memory]
[Any legal conclusion above is a starting hypothesis — research before relying on it]

分析前需验证：

[接待流程依赖的特定事实——与客户或文件确认]
[截止日期——根据实际通知/法院文件确认，而非客户记忆]
[上述任何法律结论均为初步假设——需先研究再依赖]

What this summary does NOT do

本摘要不负责的事项

This summary does not decide whether the clinic takes this case. That's your analysis and [Professor]'s judgment. It structures what the client told you so you can spend your time on the analysis instead of the write-up.

undefined

本摘要不决定诊所是否受理本案。这需要你的分析和[教授]的判断。它只是整理客户所述内容，让你能将时间用于分析而非撰写记录。

undefined

Practice-area intake template references

业务领域接待模板参考

Store practice-area-specific question sets at

references/intake-templates/[area].md

. Cold-start populates these from the professor's intake form(s); if none provided, use the defaults above.

将特定业务领域的问题集存储在

references/intake-templates/[area].md

。冷启动时从教授的接待表单中填充这些模板；若未提供，则使用上述默认内容。

What this skill does NOT do

本技能不负责的事项

Decide case acceptance. Student analyzes, professor decides.
Resolve conflicts. Flags them for the professor.
Give advice during intake. Intake is gathering; advice comes after analysis and professor review.
Produce a final document. The summary is a starting point — the student reads it, corrects anything mischaracterized, and builds the analysis from it.

决定案件受理。 由学生分析，教授决定。
解决冲突。 仅为教授标记冲突。
接待期间提供建议。 接待流程仅用于收集信息——建议需在分析和教授审核后给出。
生成最终文档。 摘要是起点——学生需阅读摘要，纠正任何错误表述，并在此基础上进行分析。

Close with the next-steps decision tree

以下一步决策树收尾

End with the next-steps decision tree per CLAUDE.md

## Outputs

. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.

根据CLAUDE.md中的

## 输出

部分，以下一步决策树收尾。根据本技能生成的内容自定义选项——五个默认分支（起草X、升级、获取更多事实、观望、其他）是起点，并非固定选项。决策树是输出内容，由律师选择后续步骤。