demand-received

Extract fields from Letters Before Action and cross-check litigation portfolio history.

9|Updated May 18, 2026
One-click install
npx skills add https://github.com/uk-agents/uk-legal-plugins --skill demand-received-uk-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demand-received
Source: https://github.com/uk-agents/uk-legal-plugins/tree/main/litigation-legal-uk/skills/demand-received
Command: npx skills add https://github.com/uk-agents/uk-legal-plugins --skill demand-received-uk-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly triage an inbound Letter Before Action (or Letter of Claim) by extracting key details, checking relevant portfolio history, assessing likely merit, and selecting the safest response path for counsel review.

Core Features & Use Cases

  • Inbound LBA/LOC triage: Extracts sender/recipient, deadlines, demand type, facts alleged, legal basis cited, threats, and settlement-communication framing for operational routing.
  • Portfolio cross-check: Scans the litigation matters log to find direct matches, precedent-type matches, and subject overlap so you can avoid duplicate/misdirected matter creation.
  • Response-option recommendation: Produces 3–4 structured response routes (substantive, holding, settlement, or ignore + preserve) with tradeoffs, plus deadline triage and immediate action checklist.
  • Guardrails for verification and privilege: Flags citations and pre-action protocol items for SME verification and explicitly treats the output as privileged/work-product.

Quick Start

Use the demand-received skill with the path to the incoming letter to generate a structured triage document and response-route recommendation for counsel review.

Frequently Asked Questions about demand-received

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

FAQPage Schema
How do I triage a Letter Before Action to meet CPR pre-action protocol deadlines?

You can triage inbound Letters of Claim by providing the document path to extract critical fields like deadlines and legal basis, cross-checking them against the litigation portfolio log to flag matches and avoid duplicate matter creation.

What response options should I consider when receiving a Letter of Claim?

Response options for a Letter of Claim include substantive, holding, settlement, or ignore and preserve routes, each presented with tradeoffs and a merit-rating to support safe escalation-hand-off decisions for counsel review.

Can I use this triage process to check inbound demands against an existing litigation portfolio?

Yes, the triage reads the configured portfolio log and risk calibration documents to cross-check inbound demands against existing matters, producing a triage output file with deadline flags for the inbound folder.

Does legal demand triage enforce privilege guardrails and citation verification?

Legal demand triage enforces privilege guardrails by explicitly treating output as work-product and flags citations alongside pre-action protocol items for SME verification without asserting legal conclusions.

What are the limitations of automated litigation triage for inbound Letters Before Action?

Automated litigation triage limitations include enforcing SME-verify citation checks without asserting legal conclusions, requiring configured risk calibration documents, and functioning strictly for routing rather than final legal determination.