Triage an inbound demand letter — extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake if escalation is warranted.
SkillScore68Maintained
Automatic
◆Legal & Contracts pack
Last verified 8/12/2026
What it changes
Passed 12 of 18 test cases with the skill, and 2 of 18 without it.
Without skill14%
With skill68%
Checks it passed that the model alone missed
Sets handoff command to /matter-intake
Flags cited legal assertions with [SME VERIFY]
Confirms that no changes will be made to _log.yaml
and 17 more in the full report
12 fixed3 passed either way7 still failing0 broke
Pass-rate lift
+55 pp
Tokens
+170%
Agent turns
0%
Response time
+6%
Model gemini-3.6-flashMeasured 8/12/2026v115 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
Triage for `/docs/nu_demand.pdf` determines the letter is a frivolous inquiry requiring no portfolio changes or new matter creation. Where should the file remain and what portfolio handoff occurs?
What was checked, without and with the skill
Checked
Without skill
With skill
Retains output file in ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/
Missed
Passed
Confirms that no changes will be made to _log.yaml
Missed
Passed
case-17 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md229 linessingle file
/demand-received
Read the incoming document from provided path.
Load ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml for portfolio cross-check.
Extract fields; cross-check portfolio; assess merit; present options with recommendation.
Write ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md. Copy or link incoming to ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/incoming.[ext].
Hand off per user choice:
Create matter → matter-intake pre-populated
Respond with counter-demand → demand-intake pre-populated
Link to existing matter → update related_matters in log
Standalone → no further action
Demand Received
Purpose
Inbound demand letters are the bread and butter of an in-house litigation practice. A small fraction need escalation; most can be handled with a structured response or a holding letter. The failure mode is treating them all alike. This skill triages, cross-checks the portfolio, and produces options.
Load context
The incoming document (user provides path or drops it in-session)
~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — scan for related matters (same counterparty, overlapping counterparties via entity relationships, or matter type + recent date)
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → risk calibration (for merit assessment), landscape (is the sender a frequent adversary?), demand-letter practice (house tone and response defaults)
Workflow
Step 1: Read the demand
Extract from the incoming:
Sender — entity, signer, counsel (if signed by outside firm)
Recipient — which entity/person at our company
Delivery — certified, email, courier (matters for deadline calculation)
Date received vs. date signed
Demand type — payment, breach/cure, C&D, preservation, settlement, other