| name | comms-improver |
| title | Comms Improver |
| description | Use when the user has a piece of legal-jargon-heavy text and wants it rewritten in plain language for a specified non-legal audience. Common scenarios — email to a business stakeholder, legal disclaimer for a customer-facing page, memo for a non-legal audience, explanation of a contract clause for a deal team, summary of a regulatory development for an executive briefing. Produces the rewritten text plus a brief explanation of what was changed and why, including any preservation-of-meaning concerns where the rewrite required interpretation. Does not draft from scratch; the input is text that exists. |
| author | LegalQuants |
| author_url | https://github.com/LegalQuants/lq-ai/tree/main/skills/comms-improver |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | general |
| language | en |
Comms Improver
Rewrite legal text in plain language for a specified non-legal audience. The output preserves meaning while changing form: shorter sentences, common words instead of jargon, active voice instead of passive, concrete examples instead of abstract formulations. The skill is transformation, not drafting from scratch.
This skill is for the everyday in-house counsel task of translating between legal precision and non-legal accessibility. Lawyers spend significant time rewriting their own work — or reviewing others' rewrites — for executive readouts, sales communications, customer disclosures, deal-team briefings, and engineering specs. The skill does this rewriting (or supports the user's rewriting) while flagging where translation involved interpretation.
When this skill applies
Apply when the user has legal-jargon-heavy text and wants it rewritten for a specified non-legal audience. Common inputs:
- Email drafts to non-legal business stakeholders.
- Contract clauses to be explained to a deal team or product team.
- Legal disclaimers to be rewritten for customer-facing surfaces.
- Memos to be summarized for executive readouts.
- Regulatory developments to be communicated to affected business functions.
- Compliance obligations to be translated for the operational owner.
Do not apply when:
- The user wants to draft text from scratch. Out of scope — the skill rewrites existing text. Drafting from scratch is a different shape (drafting skill candidate; deferred enhancement).
- The user wants to translate between languages (e.g., English to Spanish). Out of scope.
- The user wants legal review of someone else's plain-language rewrite. Out of scope; that's review, not rewriting. The user can paste both versions and ask whether the rewrite preserves meaning, but the skill is calibrated for the rewriting task.
- The text is already plain language and the user wants a different style. Out of scope; that's editing for style, not rewriting for accessibility.
- The user wants to "make this sound more legal" or "add legal weight." Out of scope — the skill goes from legal to plain, not the other direction. Adding legal precision to plain text is a different task with different risks (introducing meaning the original didn't carry).
Inputs
The skill requires the text and the audience. If audience is not provided:
"Before I rewrite, who is this for? The audience determines tone, length, and detail level. Examples:
- 'Executive readout for CEO/CFO — single paragraph'
- 'Sales team — they need to understand what they can say to prospects'
