plain-language-letters

Redirect deprecated plain-language letter drafting to /client-letter and /status client workflows.

183|37|Updated May 15, 2026
One-click install
npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill plain-language-letters-zhou210712
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plain-language-letters
Source: https://github.com/zhou210712/claude-for-legal-ZH/tree/main/legal-clinic/skills/plain-language-letters
Command: npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill plain-language-letters-zhou210712

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This deprecated skill avoids confusion by pointing users to the newer, more focused skills for generating plain-language client communications.

Core Features & Use Cases

  • Deprecated redirect: Guides users away from legacy “通俗语言信函” generation and toward the v2 replacements.
  • Separated workflows: Distinguishes between routine letters and substantive client status updates to improve consistency and outcomes.
  • Use Case: If you previously used this skill to draft a simple appointment confirmation or a brief “submission received” update, you should instead use the dedicated routine client-letter workflow.

Quick Start

Use the /client-letter skill for routine plain-language letters, or use the /status client skill for substantive client status updates.

Frequently Asked Questions about plain-language-letters

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

FAQPage Schema
Why is my plain language client letter workflow not working?▼

Your plain language client letter workflow is not working because the legacy skill is deprecated and disabled. You must migrate to the v2 replacements for routing to succeed.

How do I migrate my plain language communication drafting to the new workflow?▼

To migrate plain language communication drafting, follow the v2 routing instructions to map legacy invocations directly to the /client-letter and /status client replacement skills.

What is the difference between routine client letters and substantive status updates?▼

Routine client letters handle simple correspondence like appointment confirmations, while substantive status updates manage complex case progress, requiring two separated v2 workflows for consistency.

Can I still use this skill for legal clinic client correspondence?▼

You cannot use this skill for legal clinic client correspondence because user-invocation is disabled. You must redirect to the dedicated routine client-letter or status update workflows.

When do I need to use the /client-letter skill versus the /status client skill?▼

Use the /client-letter skill for routine plain-language letters like submission confirmations, and use the /status client skill for substantive client status updates in legal clinic workflows.