plain-language-letters

Redirect deprecated plain-language correspondence workflows to dedicated client-letter and status update skills.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/PolliticalSolutions/political-portal --skill plain-language-letters-polliticalsolutions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plain-language-letters
Source: https://github.com/PolliticalSolutions/political-portal/tree/main/.claude/skills/legal-clinic/plain-language-letters
Command: npx skills add https://github.com/PolliticalSolutions/political-portal --skill plain-language-letters-polliticalsolutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plain-Language Letters help prevent jargon-heavy or overly technical correspondence, but this specific skill is deprecated and exists only to support migration from older workflows.

Core Features & Use Cases

  • Migration redirect: Sends users to more focused replacements instead of continuing with the deprecated routine-letter workflow.
  • Routine correspondence coverage: Appointment confirms, document requests, and brief “we filed it” updates belong in the client-letter flow.
  • Substantive update coverage: Meaningful client status updates belong in the status update flow, using plain-language standards from the shared CLAUDE.md guidance.

Quick Start

Use the plain-language client letter workflow by invoking /client-letter [type] for routine correspondence.

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 client letters for routine correspondence?▼

Plain language client letters for routine correspondence like appointment confirms and document requests are handled by invoking the `/client-letter` workflow. This replaces the deprecated workflow and ensures communications remain clear and jargon-free.

What is the best way to send substantive status updates to legal clients?▼

Substantive status updates for legal clients are managed through the `/status client` workflow. This dedicated approach applies shared plain-language standards to ensure meaningful case progress is communicated clearly.

Why is my plain language correspondence workflow deprecated?▼

The plain language correspondence workflow is deprecated to support migration toward focused replacements. Older routines are redirected to dedicated client-letter and status update skills to better separate routine document requests from substantive case updates.

Can I still use the plain-language-letters skill for filing confirmations?▼

Brief filing confirmations are routed to the `/client-letter` workflow rather than the deprecated plain-language-letters skill. This ensures routine correspondence is handled by the dedicated client communication flow.

What are the limitations of using deprecated plain language legal workflows?▼

Using deprecated plain language legal workflows limits functionality because operational instructions now defer to `/client-letter` and `/status client`. The skill exists solely for migration redirect, preventing access to the older routine-letter workflow.

Does the plain-language-letters skill require specific configuration for migration?▼

Migration requires the skill's entry point to be identified by SKILL.md YAML frontmatter. Operational instructions must defer to `/client-letter` and `/status client` while preserving plain-language standards from shared guidance.