skills.rest
gtgspot
gtgspotCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

demand-received

Extract demand letter details and cross-check portfolio context to recommend actions.

Updated May 28, 2026
Search Tags:#portfolio#risk-assessment#triage#litigation#demand-letter#matter-management
One-click install
npx skills add https://github.com/gtgspot/clegal --skill demand-received-gtgspot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: demand-received
Source: https://github.com/gtgspot/clegal/tree/main/litigation-legal/skills/demand-received
Command: npx skills add https://github.com/gtgspot/clegal --skill demand-received-gtgspot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inbound demand letters in litigation are time-sensitive and require quick, structured triage to determine routing, risk, and next steps. This skill pulls the sender, demand type, delivery method, dates, and requested relief, cross-references portfolio context, and presents actionable options with recommended actions.

Core Features & Use Cases

  • Inbound demand triage: parse sender, signer, delivery, date received, date signed, demand type, specific asks, facts alleged, and legal basis.
  • Portfolio cross-check: search the portfolio log for related matters, precedents, and overlap.
  • Merit assessment & options: rate merit, outline strengths/weaknesses, and present 3-4 routing options with rationale.
  • Hand-off readiness: generate pre-populated fields for matter-intake or demand-intake and log actions.

Quick Start

Provide the inbound demand letter path to initialize the triage workflow.

Frequently Asked Questions about demand-received

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

FAQPage Schema
How do I triage inbound demand letters for litigation routing?▼

To triage inbound demand letters, this skill extracts the sender, delivery method, dates, demand type, and legal basis, then cross-references portfolio context to assess merit and generate actionable routing options.

What is the best way to assess litigation risk from a demand letter?▼

Assessing litigation risk from a demand letter involves cross-checking the extracted facts and legal basis against a portfolio log for precedents, calibrating risk, and flagging deadlines for SME verification.

How do I populate matter-intake fields from an inbound demand letter?▼

You can populate matter-intake fields by parsing the inbound demand letter path to initialize the triage workflow, which automatically generates pre-populated fields and log entries for hand-off.

Can I use portfolio context to evaluate the merit of a demand letter?▼

Yes, you can use portfolio context to evaluate demand letter merit by loading the portfolio log to search for related matters, assess precedents, and outline specific strengths and weaknesses.

What specific information is extracted during demand letter triage?▼

Demand letter triage extracts the sender, signer, delivery method, date received, date signed, demand type, specific asks, facts alleged, and the underlying legal basis to determine next steps.

When should I flag an inbound demand for SME verification?▼

You should flag an inbound demand for SME verification when the triage process identifies specific authorities and deadlines that require expert validation within your CLAUDE.md practice guidelines.

Related Skills

Explore More Legal & Compliance Skills→
bomdaybomday

is-this-a-problem

Assess legal issues in product development using predefined patterns and risk calibration.

Community
Intermediate
gtgspotgtgspot

demand-intake

Collect pre-writing inputs for demand letters and save them to intake.md.

Community
Advanced
stakworkstakwork
109

portfolio-status

Summarize litigation matter logs to identify portfolio risk and anomalies.

Official
Advanced
Bossmann007Bossmann007

demand-received

Triage demand letters by parsing contents and cross-checking portfolio data.

Community
Advanced