demand-received

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. Use when the user says "we got a demand letter", "triage this demand", or shares an incoming demand to evaluate.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a thorough, highly actionable legal-triage workflow with strong sequencing and validation gates, but it is a long single file that does not progressively disclose its large output template and rationale material into separate references, which caps conciseness and progressive disclosure at 2.

Suggestions

Move the full triage.md output template (Steps 6) into a references/triage-template.md and link to it, keeping only the field summary inline — this improves both conciseness and progressive_disclosure.

Trim the prose explanations in the privilege-inheritance and source-attribution paragraphs to bullet-style directives; the rules earn their place but the surrounding justification can be tightened.

Consider extracting the four response-option rationales (Option A–D) into a references/response-options.md referenced one level deep, leaving the workflow to list the options and link out.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and domain-specific (FRE 408 framing, source-attribution tags, privilege inheritance are things Claude would not know), but the ~230-line body and the inline triage.md template carry prose that could be tightened; not level 3 because some explanatory paragraphs pad beyond what the steps require.	2 / 3
Actionability	Concrete and specific throughout — exact field lists, exact plugin file paths, literal hand-off commands ('/demand-intake', '/matter-intake', '/legal-hold --issue'), and a copy-paste output template — matching the level-3 actionable anchor for an instruction-only skill.	3 / 3
Workflow Clarity	A clear 7-step sequence with explicit checkpoints: the 'No silent supplement' stop-and-ask rule, SME VERIFY flags, source-attribution tagging, and the immediate-actions checklist provide feedback loops and validation matching the level-3 anchor.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a single monolithic file with no bundle references — the long inline triage.md output template and option rationales are content that could be split into a reference file, matching the level-2 'content that should be separate is inline' anchor rather than the one-level-deep reference structure of level 3.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: third-person voice, concrete action list, explicit trigger phrasing, and a well-scoped niche. It cleanly satisfies all four dimensions with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'extract fields, cross-check the portfolio, assess merit, present response options with a recommendation, and hand off to matter-intake or demand-intake' — matching the level-3 anchor of several specific actions.	3 / 3
Completeness	Clearly answers both what (triage/extract/cross-check/assess/hand off) and when (explicit 'Use when the user says…' clause), matching the level-3 anchor with explicit triggers; not level 2 because the when is explicit, not merely implied.	3 / 3
Trigger Term Quality	Quotes natural user phrasings — 'we got a demand letter', 'triage this demand', 'shares an incoming demand to evaluate' — giving good coverage of terms a user would actually say, matching level 3.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche — inbound demand letter triage — with distinct triggers unlikely to fire for unrelated skills, matching the level-3 clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: anthropics/claude-for-legal
Path: litigation-legal/skills/demand-received/SKILL.md
Commit: 4a6c651

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.