Install any skill in seconds. Free to start, no credit card required.
Get Started Free →anthropics/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.
Passed 21 of 22 test cases with the skill, and 3 of 22 without it.
and 9 more in the full report
18 fixed3 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am preparing a major quarterly update for the executive team at Apex Corp explaining our defense strategy, recent deposition outcomes, and risk exposure. Which command or location should I use for this client update?
| Checked | Without skill | With skill |
|---|---|---|
| Directs the user to /status client or skills/status/ | Missed | Passed |
The instructions your model reads when the skill loads.
/client-letter and /status clientThis skill was split during the v2 rebuild:
Routine correspondence (appointment confirms, document requests, brief
"we filed it" updates) → skills/client-letter/ — use /client-letter [type]
Substantive client status updates → skills/status/ in client-facing
mode — use /status client
Both apply the plain-language standards (reading level, no jargon) from CLAUDE.md.
See the respective SKILL.md files for full workflows.
test cases passed, vs 3 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.