plain-language-letters

Reference: DEPRECATED — use `/client-letter` for routine correspondence or `/status client` for substantive updates. Split into two more focused skills during the v2 rebuild. Kept as a redirect for migration.

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./legal-clinic/skills/plain-language-letters/SKILL.md

Quality

Content

100%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 an exemplary deprecated-skill redirect: concise, fully actionable with explicit replacement commands and paths, a clear two-branch decision, and one-level-deep references to the successor SKILL.md files. It does exactly what a deprecation notice should with no wasted tokens.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~12-line redirect notice — every line earns its place by stating what moved where and how to invoke the replacements, with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	It gives concrete, copy-paste-ready invocation commands ('/client-letter [type]' and '/status client') and points to exact paths (skills/client-letter/, skills/status/), leaving no ambiguity about what to do next.	3 / 3
Workflow Clarity	For a simple single-purpose redirect skill the action is unambiguous: choose routine correspondence vs substantive update and run the named command; the two bullets cleanly partition the decision, so workflow clarity is full per the simple-skills scoring note.	3 / 3
Progressive Disclosure	The overview points one level deep to the respective SKILL.md files ('See the respective SKILL.md files for full workflows'), with no nested references and no inline bloat; references are clearly signaled and there are no bundle files to misorganize.	3 / 3
	Total	12 / 12 Passed

Description

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

This is a deprecated redirect description rather than a capability description; it clearly signals deprecation and routes to two replacement skills but describes no concrete actions of its own. It is functional for migration but weak as a standalone skill description.

Suggestions

If the skill must remain discoverable, add a one-line 'Use when...' clause clarifying that it should never be invoked directly, to make the deprecation intent explicit.

Lead with the deprecation status and the two replacement commands more concisely; trim the meta-context ('Split into two more focused skills during the v2 rebuild') which adds no actionable trigger information.

Consider whether a deprecated skill needs a description judged on capability terms at all — the routing clarity is strong but capability specificity is inherently near-zero for a redirect.

Dimension	Reasoning	Score
Specificity	The description states no concrete capabilities of this skill itself — it only says 'DEPRECATED', 'use /client-letter for routine correspondence or /status client for substantive updates', and 'Kept as a redirect for migration', which is abstract redirection language rather than named actions.	1 / 3
Completeness	It answers 'when to use' implicitly by routing to /client-letter or /status client, but for the skill itself there is no positive 'what does this do' beyond being a deprecated redirect, and no explicit 'Use when...' clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	It does surface natural terms a user might say ('routine correspondence', 'substantive updates', '/client-letter', '/status client'), but coverage is moderate and centered on redirect targets rather than a natural trigger surface for this skill.	2 / 3
Distinctiveness Conflict Risk	As an explicitly deprecated redirect it is unlikely to be actively chosen, but the description names two replacement skills whose triggers could overlap with correspondence/update requests, so it is only somewhat specific.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: anthropics/claude-for-legal
Path: legal-clinic/skills/plain-language-letters/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.