plain-language-letters

Route deprecated letter drafting to client-letter and status client skills.

100|16|Updated May 13, 2026
One-click install
npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill plain-language-letters-zekaisuni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plain-language-letters
Source: https://github.com/ZekaiSuni/claude-for-legal-turkish/tree/main/legal-clinic/skills/plain-language-letters
Command: npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill plain-language-letters-zekaisuni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plain-language client letters help produce clear, low-jargon correspondence for routine client communications, but this specific skill is deprecated in favor of more focused alternatives.

Core Features & Use Cases

  • Plain-language compliance (deprecated redirect): Uses the project’s plain-language standards to avoid jargon and keep writing client-friendly.
  • Migration to focused skills: Routes routine correspondence and substantive status updates to the appropriate newer skills.
  • Use cases: Appointment confirmations, document request messages, brief “we filed it” updates, and substantive client status update communications.

Quick Start

Use this deprecated skill only as a migration reference, and instead request routine correspondence with /client-letter and substantive updates with /status client.

Frequently Asked Questions about plain-language-letters

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write plain-language legal letters for client correspondence?

Plain-language legal letters are produced by applying repository standards for jargon avoidance and reading level to routine client correspondence. This skill maps routine drafting requests to focused alternatives for generating clear, low-jargon communications.

What is the best way to send status updates to legal clients without using jargon?

Status updates for legal clients are handled by routing substantive updates to the /status client skill. This ensures communications follow plain-language standards while delivering clear, substantive case progress information.

Can I use this skill to draft appointment confirmations and document requests?

Appointment confirmations and document request messages are supported as routine correspondence. However, this skill is deprecated and functions only as a migration reference, redirecting routine drafting to the /client-letter skill.

Why is the plain-language-letters skill marked as deprecated?

The plain-language-letters skill is deprecated because it covers migration-level behavior for letter drafting. It now functions solely as a redirect for v2 rebuilding, routing users to newer, more focused skills for client correspondence and status updates.

When should I use /client-letter instead of this deprecated drafting skill?

You should use /client-letter for all routine correspondence like appointment confirmations and document requests. This deprecated skill should only be used as a migration reference to route requests to the appropriate newer skills.

Does this skill enforce reading level standards for legal compliance letters?

Reading level standards for legal compliance letters are enforced by following the project's plain-language standards. The skill ensures jargon avoidance and client-friendly writing while mapping requests to focused v2 alternatives.