status

Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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.

A strong, actionable skill body built around three concrete templates with explicit supervision and review gates appropriate to consequential legal communications. Its only weakness is conciseness — the repeated full plugin path and a motivating Purpose paragraph could be tightened without losing substance.

Suggestions

Alias the repeated plugin path (e.g., define 'clinic config = ~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md' once) to remove the 5+ verbatim repetitions and trim tokens.

Tighten the 'Purpose' paragraph — keep one sentence on the same-facts/different-readers thesis and drop the enumeration of audiences already covered below.

Consider extracting the three full audience templates into reference files (client.md, internal.md, court.md) referenced from a lean overview, since the templates are the bulk of the body and could lighten the core SKILL.md.

Dimension	Reasoning	Score
Conciseness	The per-audience templates and include/exclude lists are dense and earn their place, but the long plugin path '~/.claude/plugins/config/claude-for-legal/legal-clinic/CLAUDE.md' is repeated 5+ times and the 'Purpose' paragraph adds motivating prose ('Clinics generate enormous numbers of status updates...') that could be trimmed.	2 / 3
Actionability	Copy-paste-ready templates per audience with concrete placeholders and plain-language examples ('We filed your answer with the court on [date]' not 'The responsive pleading was submitted') give fully actionable, specific guidance for this instruction-only skill.	3 / 3
Workflow Clarity	A clear numbered sequence (load context → generate per audience → supervision routing) with explicit validation gates: 'Before sending... Confirm the draft has been reviewed per the supervision protocol... all internal review labels... removed' and 'Court filings ALWAYS require professor review before filing'.	3 / 3
Progressive Disclosure	Well-organized into clear sections (Purpose, Load context, three Audience modes, Supervision routing, What this skill does NOT do) with a single one-level reference to the plugin CLAUDE.md, no nested references, and easy navigation; no bundle files exist to disclose further.	3 / 3
	Total	11 / 12 Passed

Description

90%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.

A well-crafted description that names a specific niche, frames three audience modes, and gives explicit natural-language triggers for both what and when. The only soft spot is specificity, since it describes one capability with three framings rather than a list of distinct actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Case status summary by audience') and three concrete variants ('client-facing', 'internal', 'court-ready'), but these are framings of one capability rather than multiple distinct actions like the anchor-3 'extract, fill, merge'.	2 / 3
Completeness	Clearly states what it does ('Case status summary by audience — ... Same facts, different framing and depth') and when to use it via an explicit 'Use when' clause with three triggers.	3 / 3
Trigger Term Quality	'Use when a student needs to update the client, brief the professor, or prepare a court status report' supplies three natural trigger phrases a clinic student would actually say, with good coverage of the domain's scenarios.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow legal-clinic niche with audience-specific triggers ('update the client', 'brief the professor', 'court status report') unlikely to overlap with or mis-trigger other skills.	3 / 3
	Total	11 / 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: legal-clinic/skills/status/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.