New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Legal Clinic Client Intake

by anthropics in anthropics/claude-for-legal

Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.

OfficialApache-2.0Auto-check passedLegal & Compliance

Install Legal Clinic Client Intake

skills CLI
$ npx skills add anthropics/claude-for-legal --skill client-intake -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install anthropics/claude-for-legal client-intake --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/legal-clinic/skills/client-intake .claude/skills/client-intake && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
client-intake
GitHub stars
9.6k
Used in
3 other repos
Token cost
~3.2k tokens
SKILL.md length
1,087 words
Files
2 (incl. references)
Skills in repo
147
Repo updated
First seen
Licence
Apache-2.0

At a glance

Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.

  • Works in 7 steps: Practice area routing → Practice-area-specific intake → Cross-practice-area issue spotting → …
  • Starting a new client intake at a legal clinic
  • SKILL.md covers Purpose, Load context, Read the supervisor guide and Workflow, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Built for law school clinics, this skill guides a student through intake interviews and writes up the result, so time goes to analysis instead of transcription. It loads clinic settings from a legal-clinic configuration file (practice areas, intake templates, supervision style, jurisdiction and flag triggers), checks for a supervisor's practice-area guide to use in place of the generic questions, and routes the client's story to the right practice-area template.

While interviewing, it listens for issues that cross practice areas, such as a housing client mentioning immigration status, and runs conflict flags and a triage classification. The output is a formatted case summary labeled as AI-assisted, with verification prompts and supervision routing for the professor. It does not decide whether the clinic accepts the case, which stays with the student's analysis and the professor's judgment.

When your agent uses it

  • Starting a new client intake at a legal clinic
  • Running an intake interview that may span several practice areas
  • Writing up a new client's situation for supervisor review
  • Flagging possible conflicts and triaging a case

Example prompts

  • “/legal-clinic:client-intake”
  • “Start an intake for a tenant facing eviction who also has questions about immigration status.”
  • “Write up my notes from today's walk-in client as an intake summary.”

Requirements

  • The legal-clinic plugin configuration with practice areas and intake templates

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Practice area routing
  2. Practice-area-specific intake
  3. Cross-practice-area issue spotting
  4. Conflict check flags
  5. Triage classification
  6. Supervision flag check
  7. Deadline handoff — required deliverable

What it can do on your machine

Read from SKILL.md and the folder at commit 4a6c651. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Legal Clinic Client Intake loads about 3.2k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 88 tokens; SKILL.md has 1,087 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from anthropics/claude-for-legal at commit 4a6c651, republished under its Apache-2.0 licence (© anthropics). 1,087 words, ~3,188 tokens.

Download SKILL.mdSave it as .claude/skills/client-intake/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
client-intake
description
Structured intake — practice-area templates, cross-area issue spotting, conflict flags, and triage classification. Produces a formatted case summary the student analyzes and the professor reviews. Does NOT decide case acceptance. Use when starting a new client intake, running an intake interview, or writing up a new client's situation.
argument-hint
[optional: practice area hint]

/client-intake

  1. Load ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md → practice areas, intake templates, supervision style, flag triggers.
  2. Use the workflow below.
  3. Route to practice-area template. Listen for cross-area issues throughout.
  4. Conflict check flags. Triage classification.
  5. Output formatted case summary with AI-assisted label, verification prompts, supervision routing.
/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.

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.

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.

Workflow

Step 1: Practice area routing

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

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
Step 3: Cross-practice-area issue spotting

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

Client saysAlso 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.

Step 4: Conflict check flags

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.

Show full SKILL.md (439 more words)Show less
Step 5: Triage classification

Not a case-acceptance decision — a triage input:

ClassificationMeans
UrgentDeadline in days, safety issue, irreversible harm imminent
Time-sensitiveDeadline in weeks, harm ongoing but not immediately irreversible
StandardNo immediate deadline, can queue normally
May be out of scopeIssue is outside clinic's practice areas — flag for referral assessment
Step 6: Supervision flag check

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.

Step 7: Deadline handoff — required deliverable

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.

Output

markdown
# Intake Summary: [Client name or 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]

## Bottom line

[Take the case / Decline because X / Need more info on Y — next step is 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.*

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

### 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.]

## 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]

## 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.

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.

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.

© anthropics, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in legal-clinic/skills/client-intake of anthropics/claude-for-legal.

  • SKILL.md
  • references/intake-templates/README.md

Open the folder on GitHubat commit 4a6c651

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in anthropics/claude-for-legal, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Legal Clinic Client Intake next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Legal Clinic Client Intake compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Legal Clinic Client Intake this skillanthropics/claude-for-legal9.6k3 repos~3.2kAutomated safety check: PassApache-2.0
Researchalirezarezvani/claude-skills28k—~4.3kAutomated safety check: PassMIT
Skill Auditoraipoch/medical-research-skills2k—~6.9kAutomated safety check: PassMIT
Nist Pf Governmukul975/Privacy-Data-Protection-Skills295—~2.2kAutomated safety check: PassApache-2.0
Patsnap Ip Innovation Coursespatsnap/mcp112—~651Automated safety check: PassApache-2.0
Paper to Chinese Patent DrafterYuan1z0825/nature-skills46k1 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Research

    alirezarezvani/claude-skills

    Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants…

    28k GitHub stars~4.3k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

  • Skill Auditor

    aipoch/medical-research-skills

    A comprehensive auditor for any agent skill — including Manus, OpenClaw/ClawHub, Claude, LobeHub, or custom SKILL.md-based skills.

    2k GitHub stars~6.9k tokensUpdated 20 days ago
    Legal & ComplianceAuto-check passed

  • Nist Pf Govern

    mukul975/Privacy-Data-Protection-Skills

    Implement the NIST Privacy Framework GOVERN function covering GV.AT awareness and training, GV.MT monitoring and review, GV.PO policy development, and GV.RR roles and responsibilities.

    295 GitHub stars~2.2k tokensUpdated 6 mo ago
    Legal & ComplianceAuto-check passed

  • Patsnap Ip Innovation Courses

    patsnap/mcp

    Patsnap IP & Innovation Courses MCP for AI agents. An agent skill from patsnap/mcp.

    112 GitHub stars~651 tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

  • Paper to Chinese Patent Drafter

    Yuan1z0825/nature-skills

    Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.

    46k GitHub starsUsed in 1 repo~1.1k tokens
    Legal & ComplianceAuto-check passed

  • C15t

    c15t/c15t

    Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.

    1.9k GitHub starsUsed in 1 repo~1.6k tokens
    Legal & ComplianceAuto-check passed

More from anthropics/claude-for-legal

All 147 skills in this repo

  • Supervisor Review Queue

    anthropics/claude-for-legal

    Official

    Holds student work in a queue for a legal clinic professor to approve, edit-then-approve or return before anything reaches clients or courts.

    9.6k GitHub starsUsed in 3 repos~1.1k tokens
    Auto-check passed

  • Tabular Document Review

    anthropics/claude-for-legal

    Official

    Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.

    9.6k GitHub starsUsed in 3 repos~4.3k tokens
    Auto-check passed

  • Product Launch Legal Review

    anthropics/claude-for-legal

    Official

    Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.

    9.6k GitHub starsUsed in 2 repos~5k tokens
    Auto-check passed

  • Legal Skills Registry Browser

    anthropics/claude-for-legal

    Official

    Searches watched registries for community legal skills, shows matches with descriptions and offers the full SKILL.md before anything is installed.

    9.6k GitHub starsUsed in 2 repos~620 tokens
    Auto-check passed

  • Contract Renewal Tracker

    anthropics/claude-for-legal

    Official

    Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.

    9.6k GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

  • EU AI Act System Inventory

    anthropics/claude-for-legal

    Official

    Maintains a register of AI systems under the EU AI Act, recording each system's role and risk tier separately, because both can differ from one system to the next.

    9.6k GitHub starsUsed in 3 repos~2.8k tokens
    Auto-check passed

Categories

Questions about Legal Clinic Client Intake

What does Legal Clinic Client Intake do?

Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification. Built for law school clinics, this skill guides a student through intake interviews and writes up the result, so time goes to analysis instead of transcription. It loads clinic settings from a legal-clinic configuration file (practice areas, intake templates, supervision style, jurisdiction and flag triggers), checks for a supervisor's practice-area guide to use in place of the generic questions, and routes the client's story to the right practice-area template.

When should I use Legal Clinic Client Intake?

Legal Clinic Client Intake fits situations like: starting a new client intake at a legal clinic; running an intake interview that may span several practice areas; writing up a new client's situation for supervisor review; flagging possible conflicts and triaging a case.

How do I install Legal Clinic Client Intake in Claude Code?

Run `npx skills add anthropics/claude-for-legal --skill client-intake -a claude-code`. Or copy the skill folder (legal-clinic/skills/client-intake in anthropics/claude-for-legal) into .claude/skills/client-intake in your project. Claude Code loads it when a task matches its description.

How do I install Legal Clinic Client Intake in Codex?

Run `npx skills add anthropics/claude-for-legal --skill client-intake -a codex`. Or copy the skill folder (legal-clinic/skills/client-intake in anthropics/claude-for-legal) into .agents/skills/client-intake in your project. Codex loads it when a task matches its description.

Can I use Legal Clinic Client Intake in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add anthropics/claude-for-legal --skill client-intake -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-intake, .gemini/skills/client-intake, .github/skills/client-intake and .opencode/skills/client-intake in your project.

What does Legal Clinic Client Intake need to run?

SKILL.md names no scripts, command-line tools or credentials: Legal Clinic Client Intake is instructions for the agent only. Our summary lists: The legal-clinic plugin configuration with practice areas and intake templates.

Does Legal Clinic Client Intake access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Legal Clinic Client Intake safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Legal Clinic Client Intake use?

Legal Clinic Client Intake is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Legal Clinic Client Intake use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 193 tokens, read only when the agent opens those files.

What are the alternatives to Legal Clinic Client Intake?

Skills that share tags, products or a category with Legal Clinic Client Intake: Research (alirezarezvani/claude-skills, 28k stars), Skill Auditor (aipoch/medical-research-skills, 2k stars), Nist Pf Govern (mukul975/Privacy-Data-Protection-Skills, 295 stars) and Patsnap Ip Innovation Courses (patsnap/mcp, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Legal Clinic Client Intake?

anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,611 GitHub stars. The repository holds 147 skills in this directory. The repository was last updated on September 29, 2026.

Source: anthropics/claude-for-legal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.