demand-received

Extract demand letter fields, cross-check portfolio, and recommend response actions.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/PolliticalSolutions/political-portal --skill demand-received-polliticalsolutions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demand-received
Source: https://github.com/PolliticalSolutions/political-portal/tree/main/.claude/skills/litigation-legal/demand-received
Command: npx skills add https://github.com/PolliticalSolutions/political-portal --skill demand-received-polliticalsolutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps triage inbound demand letters by extracting key facts, cross-checking your existing litigation portfolio, assessing initial merit and risks, and producing actionable response options with a clear handoff recommendation.

Core Features & Use Cases

  • Demand-letter extraction & structuring: Captures sender/recipient, dates, demand type, specific asks, alleged facts, legal basis cited, threats, and settlement-communication framing for triage.
  • Portfolio cross-check: Compares the demand’s counterparties and subject matter against litigation-legal/matters/_log.yaml to identify direct matches, precedent patterns, and overlap.
  • Merit triage with response routing: Produces a triage rating (substantial/debatable/weak/frivolous) and recommends a practical next action among substantive response, holding letter, settlement response, or ignore-and-preserve, including deadline triage guidance.
  • Safe verification posture: Flags cited authorities for SME verification and enforces a “stop if low coverage in research tool” rule rather than hallucinating legal answers.
  • Privileged workflow outputs: Writes a structured triage document to the inbound triage path and prepares the right handoff to matter-intake or demand-intake.

Quick Start

Use the demand-received skill to triage the incoming demand letter file at /path/to/demand-letter.pdf.

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 to determine the right response?

To triage an inbound demand letter, extract key facts like specific asks and legal basis, cross-check the counterparties against your litigation portfolio log, and generate a structured response recommendation with explicit deadlines and handoffs.

What is the best way to assess the initial merit of a demand letter?

Assessing demand letter merit involves rating the claim as substantial, debatable, weak, or frivolous, and then matching that rating to a practical next action like a substantive response, holding letter, settlement response, or ignore-and-preserve strategy.

How does portfolio cross-checking work when evaluating a demand letter?

Portfolio cross-checking compares the demand letter's counterparties and subject matter against your existing matters log to identify direct matches, precedent patterns, and overlap, ensuring informed litigation triage and response routing.

Can I use this triage process if I need to verify legal citations in a demand letter?

Yes, the triage process flags cited authorities for SME verification and enforces a stop rule if research tool coverage is low, preventing hallucinated legal answers and ensuring a safe verification posture for your legal team.

What response options are available after triaging a demand letter?

After triaging a demand letter, you can choose among a substantive response, holding letter, settlement response, ignore-and-preserve, or escalation, with the triage output document preparing the right handoff to matter-intake or demand-intake.

Do I need a configured litigation portfolio log to triage incoming demands?

Yes, triaging inbound demands requires reading a configured portfolio log and legal calibration documents to cross-check subject matter, identify precedent patterns, and write structured triage output into the inbound triage location.