New: 98,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

Demand Received

by anthropics in anthropics/claude-for-legal

Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if…

OfficialApache-2.0Auto-check passedLegal & Compliance

Install Demand Received

skills CLI
$ npx skills add anthropics/claude-for-legal --skill demand-received -a claude-code

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

GitHub CLI
$ gh skill install anthropics/claude-for-legal demand-received --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/litigation-legal/skills/demand-received .claude/skills/demand-received && 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
demand-received
GitHub stars
9.6k
Used in
2 other repos
Token cost
~3.4k tokens
SKILL.md length
1,243 words
Files
1
Skills in repo
147
Repo updated
First seen
Licence
Apache-2.0

At a glance

Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if…

  • Works in 7 steps: Read the demand → Portfolio cross-check → Merit assessment → …
  • The user says we got a demand letter
  • SKILL.md covers Purpose, Load context, Workflow and Close with the next-steps…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Demand Received is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted. Use when the user says "we got a demand letter", "triage this demand", or shares an incoming demand to evaluate.

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Legal & Compliance, covering Dispute resolution and Legal research. The repository describes itself as: A suite of plugins for legal workflows. The licence is Apache-2.0.

When your agent uses it

  • The user says we got a demand letter
  • Triage this demand
  • Shares an incoming demand to evaluate

Example prompts

  • “we got a demand letter”
  • “triage this demand”
  • “/demand-received”

Workflow steps

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

  1. Read the demand
  2. Portfolio cross-check
  3. Merit assessment
  4. Response options
  5. Deadline triage
  6. Write triage
  7. Hand off

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

Demand Received loads about 3.4k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 1,243 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~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,243 words, ~3,365 tokens.

Download SKILL.mdSave it as .claude/skills/demand-received/SKILL.md (or your agent's skills folder).
name
demand-received
description
Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted. Use when the user says "we got a demand letter", "triage this demand", or shares an incoming demand to evaluate.
argument-hint
[path-to-incoming] [--slug=custom-slug]

/demand-received

  1. Read the incoming document from provided path.
  2. Load ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml for portfolio cross-check.
  3. Load ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → risk calibration, landscape, demand-letter practice.
  4. Follow the workflow and reference below.
  5. Extract fields; cross-check portfolio; assess merit; present options with recommendation.
  6. Write ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md. Copy or link incoming to ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/incoming.[ext].
  7. Hand off per user choice:
    • Create matter → matter-intake pre-populated
    • Respond with counter-demand → demand-intake pre-populated
    • Link to existing matter → update related_matters in log
    • Standalone → no further action

Demand Received

Purpose

Inbound demand letters are the bread and butter of an in-house litigation practice. A small fraction need escalation; most can be handled with a structured response or a holding letter. The failure mode is treating them all alike. This skill triages, cross-checks the portfolio, and produces options.

Load context

  • The incoming document (user provides path or drops it in-session)
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — scan for related matters (same counterparty, overlapping counterparties via entity relationships, or matter type + recent date)
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → risk calibration (for merit assessment), landscape (is the sender a frequent adversary?), demand-letter practice (house tone and response defaults)

Workflow

Step 1: Read the demand

Extract from the incoming:

  • Sender — entity, signer, counsel (if signed by outside firm)
  • Recipient — which entity/person at our company
  • Delivery — certified, email, courier (matters for deadline calculation)
  • Date received vs. date signed
  • Demand type — payment, breach/cure, C&D, preservation, settlement, other
  • Specific asks — what they want, by when
  • Facts alleged — their version of what happened
  • Legal basis — statutes, contract provisions, theories they cite
  • Threats — what they say they'll do if we don't comply
  • Settlement-communication framing — research the settlement-communication protections applicable in the forum (FRE 408 in federal, the state equivalent otherwise). Note whether the demand is marked as a settlement communication, but remember: protection attaches from conduct and context, not merely from labeling. Capture both the label (if any) and a first-pass read of whether the substance is in fact a compromise discussion.
Step 2: Portfolio cross-check

Search _log.yaml for:

  • Direct match — matter with same counterparty (their slug matches the sender)
  • Type match — similar matter type with this counterparty in the past (closed matters count — they inform pattern)
  • Subject overlap — matters where the subject might be the same dispute (e.g., same contract, same product, same project)

Present findings:

  • If direct match + active: flag as almost certainly the same matter; recommend adding incoming to the existing matter, not opening a new one. Update related_matters if it's a tangent.
  • If direct match + closed: flag — counterparty is back. May be a new dispute (open new matter) or a resurrected one (reopen or amend). User decides.
  • If type match: note as precedent/context; probably distinct matter but inform the response strategy.
  • If no match: novel. Treat as fresh.
Step 3: Merit assessment

Not a legal opinion — a structured read:

  • Facts — do the alleged facts align with what we know? Where's the disconnect?
  • Legal basis — are the cited provisions/statutes actually applicable? (Flag cites for user verification — do not attempt to validate law autonomously.)
  • Strength on their side — if they went to court tomorrow, what's their story?
  • Strength on our side — what are our likely defenses?
  • Damages demanded vs. likely — is the ask proportionate to what a court would award if they won?
  • Leverage and pressure — are they credibly prepared to sue? Do they have capacity? Are they a repeat-litigant adversary per ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md?

Output a triage rating: substantial merit / debatable / weak / frivolous. Be blunt. The user is triaging, not writing the brief.

Step 4: Response options

Present 3-4 options with tradeoffs:

Option A — substantive response

  • When: their demand has merit or is at least debatable; a reasoned reply protects the record
  • Tradeoff: commits us to a position in writing
  • Next step: /demand-intake with pre-populated fields for a counter-response letter

Option B — holding letter

  • When: need time to investigate; don't want to concede anything or trigger their deadline math
  • Tradeoff: doesn't resolve anything; buys 2-4 weeks
  • Next step: short acknowledgment draft

Option C — settlement response

  • When: early resolution is cheaper than litigation; willing to discuss without admitting
  • Tradeoff: settlement-communication posture required — research the applicable rule (FRE 408 or state equivalent) and structure the response so the substance, not just the label, qualifies as a compromise discussion. Must be careful not to waive claims.
  • Next step: /demand-intake with type: settlement-response

Option D — ignore + preserve

  • When: demand is frivolous or the deadline doesn't create legal prejudice
  • Tradeoff: silence can be used against us in some contexts (e.g., account stated); legal hold still required
  • Next step: issue legal hold via /legal-hold --issue if not already; log the demand and move on

Recommend one. Be specific about why.

Show full SKILL.md (486 more words)Show less
Step 5: Deadline triage
  • Their stated deadline — note it, but it doesn't bind us
  • Our internal deadline — when we must decide (often: stated deadline minus 5 business days to draft + approve)
  • Legal deadlines — statute of limitations, contractual cure periods, procedural requirements

Flag any legal deadlines that are tight. Calendar them.

No silent supplement. If the inbound demand cites rules, cases, or statutes that require verification, and a research query to the configured legal research tool (Westlaw, CourtListener, Trellis, Descrybe, or firm platform) returns few or no results for a given authority, report what was found and stop. Do NOT fill the gap from web search or model knowledge without asking. Say: "The search returned [N] results from [tool]. Coverage appears thin for [cite / doctrine]. Options: (1) broaden the search query, (2) try a different research tool, (3) search the web — results will be tagged [web search — verify] and should be checked against a primary source before relying, or (4) leave the [SME VERIFY] flag and stop here. Which would you like?" A lawyer decides whether to accept lower-confidence sources; the skill does not decide for them.

Source attribution. Tag every citation carried into the triage — including the sender's cited authorities, our response-option rationales, and any research pulled for merit assessment — with where it came from: [Westlaw], [CourtListener], [Trellis], [Descrybe], or the MCP tool name for citations retrieved from a legal research connector; [web search — verify] for web-search citations; [model knowledge — verify] for citations recalled from training data; [user provided] for citations supplied in the demand itself. Citations tagged verify carry higher fabrication risk and should be checked first. Never strip or collapse the tags.

Step 6: Write triage

Output: ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md.

markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]

> **Privilege inheritance.** This triage is derived from the inbound demand and from the portfolio log, and it records our first-pass merit read and response posture. Those internal analyses are attorney-client and/or work-product material. Distributing this triage beyond the privilege circle — including forwarding it to the business lead without marking, sharing with the counterparty, or attaching to an insurance tender without scrubbing — can waive protection over both this document and the reasoning inside it. Store with privileged matter material, mark consistently with house privilege conventions, and make distribution decisions deliberately.

# Demand Received — Triage

> **READ FOR TRIAGE, NOT OPINION.** This document is an intake scan and an options analysis — not a legal merit opinion. The `Triage rating` below is a structured read to support the counsel's decision on how to route the demand. It is not a recommendation on the merits and does not substitute for case-specific legal analysis. Every cited statute, rule, or case is flagged for SME verification; every merit call is the counsel's, not this skill's.

**Slug:** [slug]
**Received:** [YYYY-MM-DD]
**Received by:** [entity / person]
**Incoming file:** [path]

---

## The demand

**Sender:** [entity, signer, counsel]
**Demand type:** [type]
**Specific asks:** [list]
**Their stated deadline:** [date]
**Settlement-communication framing:** [labeled / substantively / neither / ambiguous] — *protection turns on conduct and context, not the label; `[SME VERIFY]` against the forum's applicable rule*

## Facts alleged

[their version, in one paragraph]

## Legal basis cited

[citations — each inline-flagged with `[SME VERIFY: applicability / currency / jurisdiction]` — do not rely on any citation here without independent check]

## Threats / next steps they state

[list]

---

## Portfolio cross-check

**Direct match:** [slug if exists, or "none"]
**Type match / precedent:** [list or "none"]
**Subject overlap:** [list or "none"]
**Recommendation:** [new matter / add to existing / link via related_matters / standalone inbound]

---

## Merit assessment

**Facts:** [alignment with our version; disconnects]
**Legal basis:** [applicability, with flags]
**Their case if litigated:** [one paragraph]
**Our defenses:** [one paragraph]
**Damages proportionality:** [assessment]
**Credibility of threat:** [will they sue? capacity? repeat litigant?]

**Triage rating:** [substantial / debatable / weak / frivolous] — *structured read for routing, not a merit opinion; `[SME VERIFY: counsel to confirm before relying on this]`*

---

## Response options

### A. Substantive response
[Rationale, tradeoffs, next step]

### B. Holding letter
[Rationale, tradeoffs, next step]

### C. Settlement response
[Rationale, tradeoffs, next step]

### D. Ignore + preserve
[Rationale, tradeoffs, next step]

**Recommendation:** [A/B/C/D] — [two sentences why] — `[SME VERIFY: counsel to confirm before executing]`

---

## Deadlines

- **Their stated deadline:** [date]
- **Our internal decision deadline:** [date]
- **Legal deadlines:** [SoL, cure periods, procedural — with dates]

---

## Immediate actions

- [ ] Legal hold issued — [yes/no] — if no, run `/legal-hold [slug] --issue`
- [ ] Matter created in log — [yes/no/TBD]
- [ ] Counsel assigned — [who]
- [ ] Insurance tendered — [yes/no/N-A]
- [ ] Internal escalation (GC/CFO/business lead) — [who/when]
Step 7: Hand off

Based on recommendation and user confirmation:

  • Matter creation → hand off to /matter-intake with: counterparty, type, source: demand-letter (inbound), initial theory framed defensively, pre-populated.
  • Counter-response as outbound demand → hand off to /demand-intake with: counterparty, context from triage, desired outcome as the response.
  • Link to existing matter → update that matter's related_matters in _log.yaml; append event to its history.md.
  • Standalone → leave in ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/; no portfolio change.

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.

What this skill does not do

  • Validate cited law. Flags cites for the user to run through a citator (verify it is good law) or check with outside counsel. Inventing legal analysis on inbound demands is malpractice exposure.
  • Send a response. Drafts are drafted in demand-draft; this skill stops at the triage decision.
  • Decide merit definitively. The rating is a read for triage; a formal merit opinion lives with outside counsel or more thorough analysis.
  • Make the matter-creation call. Surfaces the recommendation; user decides.

© 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

Just SKILL.md in litigation-legal/skills/demand-received of anthropics/claude-for-legal.

Open the folder on GitHubat commit 4a6c651

Used in 2 other repositories

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 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

Demand Received 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.

Demand Received compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Demand Received this skillanthropics/claude-for-legal9.6k2 repos~3.4kAutomated safety check: PassApache-2.0
Litigation Deadline Calendarlawve-ai/awesome-legal-skills842—~4.3kAutomated safety check: PassMIT
Moot Court Simulation Buildercat-xierluo/legal-skills717—~1.4kAutomated safety check: PassCC-BY-NC-4.0
Tw Legal RAGaa0101181514/tw-legal-rag328—~580Automated safety check: PassCustom licence
Design Award SearchSeanJ1ang/design-judge-skills712—~3kAutomated safety check: PassApache-2.0
China Lawyer AnalystCSlawyer1985/china-lawyer-analyst196—~3.3kAutomated safety check: PassNone

Similar skills

  • Litigation Deadline Calendar

    lawve-ai/awesome-legal-skills

    Calendar litigation and arbitration deadlines from a scheduling order.

    842 GitHub stars~4.3k tokensUpdated 6 days ago
    Legal & ComplianceAuto-check passed

  • Moot Court Simulation Builder

    cat-xierluo/legal-skills

    Chinese-language skill that organizes a case file into a multi-role mock trial with judge, parties and clerk, producing a transcript, issue review and a to-strengthen list.

    717 GitHub stars~1.4k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed

  • Tw Legal RAG

    aa0101181514/tw-legal-rag

    Retrieve real Taiwan court judgments with verifiable citations before answering any question about Taiwan law or case law.

    328 GitHub stars~580 tokensUpdated today
    Legal & ComplianceAuto-check passed

  • Design Award Search

    SeanJ1ang/design-judge-skills

    Find and verify award-winning designs in the same or adjacent functional category through eight explicit relevance dimensions: problem and user, core function, sensing technology, intervention…

    712 GitHub stars~3k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

  • China Lawyer Analyst

    CSlawyer1985/china-lawyer-analyst

    通过中国法律视角分析事件，运用成文法解释、指导案例参照、请求权基础分析等方法， 理解权利义务、评估责任风险、识别法律依据并推荐合规策略。

    196 GitHub stars~3.3k tokensUpdated 8 mo ago
    Legal & ComplianceAuto-check passed

  • Billing And Litigation Budget

    THUYRan/Legal-Skills-Chinese

    A skill your agent uses when the user needs to track or manage attorney hours, expert fees, and investigation costs; control litigation spend; or prepare timesheets or expense statements for clients.

    873 GitHub stars~5k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

More from anthropics/claude-for-legal

All 147 skills in this repo

  • Legal Clinic Client Intake

    anthropics/claude-for-legal

    Official

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

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

  • 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

Categories

Questions about Demand Received

What does Demand Received do?

Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if…. Demand Received is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted.

When should I use Demand Received?

Demand Received fits situations like: the user says we got a demand letter; triage this demand; shares an incoming demand to evaluate.

How do I install Demand Received in Claude Code?

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

How do I install Demand Received in Codex?

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

Can I use Demand Received 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 demand-received -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/demand-received, .gemini/skills/demand-received, .github/skills/demand-received and .opencode/skills/demand-received in your project.

What does Demand Received need to run?

SKILL.md names no scripts, command-line tools or credentials: Demand Received is instructions for the agent only.

Does Demand Received 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 Demand Received 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 Demand Received use?

Demand Received 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 Demand Received use?

About 3.4k 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.

What are the alternatives to Demand Received?

Skills that share tags, products or a category with Demand Received: Litigation Deadline Calendar (lawve-ai/awesome-legal-skills, 842 stars), Moot Court Simulation Builder (cat-xierluo/legal-skills, 717 stars), Tw Legal RAG (aa0101181514/tw-legal-rag, 328 stars) and Design Award Search (SeanJ1ang/design-judge-skills, 712 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Demand Received?

anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,629 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.