demand-received

Extract key fields from legal correspondence and propose routing options.

183|37|Updated May 15, 2026
One-click install
npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill demand-received-zhou210712
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demand-received
Source: https://github.com/zhou210712/claude-for-legal-ZH/tree/main/litigation-legal/skills/demand-received
Command: npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill demand-received-zhou210712

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps legal teams triage incoming demand letters or other legal correspondence by extracting key facts, finding related litigation patterns, and proposing structured response options for attorney review.

Core Features & Use Cases

  • Inbound Triage & Field Extraction: Extracts sender/recipient, delivery/signature dates, letter type, demands, asserted facts, legal bases, and threats from the provided document.
  • Cross-Case Combination via Local Matter Logs: Loads the existing litigation matter log to suggest whether the letter belongs to an existing case, a new case, or related matter context.
  • Structured Routing Recommendation: Produces a triage document with a risk-calibrated “substance strength” rating and selects among reply/hold/archival routing paths, including next-step handoff instructions for intake drafts.

Quick Start

Use the demand-received skill with the attached file and let it generate the triage document for routing decisions, e.g., “Run demand-received on the file inbound-letter.pdf and save results under a triage slug.”

Frequently Asked Questions about demand-received

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage an incoming demand letter for attorney review?

To triage a demand letter, the Skill extracts key fields like delivery dates, demands, and legal bases, cross-references local litigation logs, and generates a structured triage document with response routing options for attorney review.

What is legal triage for inbound correspondence and litigation routing?

Legal triage for inbound correspondence involves extracting critical facts from demand letters, matching them against existing case logs, and proposing risk-calibrated routing paths for new case intake, drafting, or archiving.

How do I extract key fields and assess risk from a demand letter?

You can extract key fields and assess risk by processing the demand letter through the Skill, which identifies asserted facts, evaluates substance strength, and applies risk calibration to produce attorney-review-first guidance with citation labels.

Can I use local litigation logs to route a new demand letter to an existing case?

Yes, the Skill loads local litigation matter logs to cross-reference the inbound demand letter, determining whether it belongs to an existing case, requires new case intake, or needs association with related matters.

What's the best way to generate a structured intake draft from a demand letter?

The best way to generate an intake draft is to run the Skill on the inbound file, which produces a triage.md file containing substance strength ratings, routing paths, and next-step handoff instructions for drafting.

Do I need a local triage path configured to process demand letters?

Yes, you need a local triage path configured so the Skill can write the generated triage.md file, alongside loading local litigation logs and configuration context required for cross-referencing matter history.