demand-received

Extract demand letter fields, cross-check litigation portfolio, and recommend routing decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an inbound demand letter into a structured triage that extracts key fields, checks for portfolio matches, and recommends the right next workflow step without overstepping into an unverified legal opinion.

Core Features & Use Cases

  • Demand triage & field extraction: Pulls sender/recipient, dates, demand type, asks, alleged facts, cited legal basis, threats, and settlement-communication posture.
  • Portfolio cross-check: Compares the incoming demand against litigation-legal/matters/_log.yaml to identify direct matches, similar precedent, and subject overlap.
  • Merit routing with guardrails: Produces a triage rating (substantial/debatable/weak/frivolous) and response options (substantive, holding, settlement response, ignore + preserve) with deadline scanning.
  • Verification-aware citations: Enforces SME verification flags and stops when research coverage is thin.

Quick Start

Use demand-received on the incoming demand file path you provide, so it outputs a triage decision document in the configured inbound slug folder.

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 inbound demand letter and extract key fields?

Demand triage involves extracting key fields like sender, dates, alleged facts, and cited legal basis from the inbound letter, then producing structured response options with a recommended routing decision.

What is litigation portfolio cross-checking for demand letters?

Litigation portfolio cross-checking compares incoming demand letters against an existing matters log to identify direct matches, similar precedent, and subject overlap for routing decisions.

How do I route a demand letter based on legal merit?

Routing a demand letter by merit involves assigning a triage rating of substantial, debatable, weak, or frivolous, then generating response options like substantive, holding, settlement, or ignore with preservation.

How does deadline analysis work for settlement communications?

Deadline analysis scans the settlement communication posture and response deadlines within the demand letter to ensure timely routing and prevent missing critical legal response windows.

Can I use this demand triage workflow without SME verification for cited authorities?

No, this workflow enforces SME verification flags for cited legal authorities and halts the triage process when research coverage is insufficient to avoid overstepping into unverified legal opinions.

What's the best way to generate response options for a frivolous demand letter?

For frivolous demand letters, the triage process recommends an ignore and preserve response option, backed by a weak merit rating and verification flags for any cited authorities requiring SME confirmation.