client-email

Solid

Draft client-facing emails for legal services — cover notes for contract deliverables, redline summaries, deal status updates, and follow-ups. Use when composing or revising outbound emails to clients about legal work product. Triggers on "draft reply," "email to client," "cover note," "write back to," or any outbound email accompanying a legal deliverable.

AI & Automation 34 stars 5 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
51
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# client-email Style and formatting rules for drafting client-facing emails that accompany legal work product — contract redlines, new drafts, deal summaries, and follow-ups. ## Security model - This skill is **guidance only** — it does not send emails, call APIs, or access external systems. - All output is draft text for the user to review and send manually. - Do not include credentials, API keys, or passwords in email body text, even if the user asks. ## When to use Apply these rules when drafting or revising an outbound email from a lawyer or legal services provider to a client. Designed for emails that accompany deliverables (revised contracts, redlines, memos) or communicate legal analysis to non-lawyer business clients. Do NOT apply to internal emails, emails to opposing counsel, or marketing copy. ## Email structure The numbered-list structure below is for substantive cover notes with multiple topics. Short emails with a single paragraph of content should be written naturally without numbered items. ``` [Cover line: 1-3 sentences. Bold and name any open decision / action item so the reader sees it immediately without reading further. E.g., "the **one open item (indemnity cap)** that needs your input."] 1. **Declarative heading that conveys the takeaway.** Discussion. **_a. Bold-italic lettered sub-item_**_._ Discussion of sub-point. **_b. Another sub-item_**_._ Discussion. 2. **Another declarative heading.** Discussion. Not every item needs sub-points. 3. ...

Details

Author
open-agreements
Repository
open-agreements/open-agreements
Created
3 months ago
Last Updated
today
Language
TypeScript
License
MIT

Integrates with

Related Skills