plain-language-letters

Redirect users to focused client-letter and status skills for correspondence.

Updated May 28, 2026
One-click install
npx skills add https://github.com/gtgspot/clegal --skill plain-language-letters-gtgspot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plain-language-letters
Source: https://github.com/gtgspot/clegal/tree/main/legal-clinic/skills/plain-language-letters
Command: npx skills add https://github.com/gtgspot/clegal --skill plain-language-letters-gtgspot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference: this skill is deprecated and serves as a migration redirect to more focused client-letter and status update skills. It documents legacy plain-language letter workflows while guiding users to the updated tooling.

Core Features & Use Cases

  • Legacy guidance for routine client communications and status updates, with a path to migrate to /client-letter and /status client skills.
  • Clear mapping from old templates to new, focused workflows to preserve continuity during transition.
  • Provides a stepping-stone in enterprise deployment to avoid disruption while replacing monolithic plain-language letters with targeted actions.

Quick Start

Use /client-letter for routine correspondence and /status client for substantive updates.

Frequently Asked Questions about plain-language-letters

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

FAQPage Schema
How do I migrate legacy plain-language client letters to focused workflows?

This skill redirects legacy plain-language client letters to focused workflows, documenting the migration path to targeted client-letter and status update skills while ensuring compatibility with existing CLAUDE.md guidelines during stepwise deprecation.

What is the best way to handle status updates for legal clients during a workflow migration?

For status updates during workflow migration, this skill redirects substantive client communications to the /status client workflow, preserving continuity while replacing monolithic plain-language letters with targeted actions and avoiding deployment disruption.

Can I use this skill to generate routine client correspondence without migrating?

You cannot generate routine correspondence directly; this deprecated skill redirects users to the /client-letter workflow for routine correspondence and the /status client workflow for substantive updates, functioning solely as a migration bridge.

Does this migration redirect maintain compatibility with existing CLAUDE.md guidelines?

Yes, the migration redirect maintains compatibility with existing CLAUDE.md guidelines by documenting legacy plain-language letter workflows and mapping old templates to new focused workflows, ensuring a smooth transition during enterprise deployment.

Why are monolithic plain-language letters being replaced with targeted legal workflows?

Monolithic plain-language letters are being replaced with targeted legal workflows to enable stepwise deprecation and avoid disruption, providing focused client-letter and status update capabilities that preserve continuity during enterprise migration.