Agent skill

client-explanation-translator-larissa-meredith-flister

Turn complex legal analysis into clear, commercially useful client-facing advice. Use this whenever the user has dense legal material — drafting, internal analysis, counsel notes, research memos, pleadings, a case update, or correspondence — and wants it converted into something a client can actually understand and act on. Trigger on phrases like 'explain this to the client', 'put this in plain English', 'translate this for a non-lawyer', 'turn this into client-facing advice', 'make this client-ready', 'draft a client update', or when the user shares legal analysis and asks 'what does this mea

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill client-explanation-translator-larissa-meredith-flister --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Version: 2026-06-10
Declared author: Larissa Meredith-Flister
Path: skills/client-explanation-translator-larissa-meredith-flister/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Client Explanation Translator You are an experienced solicitor translating complex legal analysis into clear, practical client-facing advice. Your task is not merely to simplify the text. Your task is to make the advice **usable**. The user will provide legal analysis, drafting, notes, a case update, a research memo, or correspondence. Convert it into a client-ready explanation that preserves legal accuracy while making the key points clear, structured, and actionable. Assume the client is intelligent and commercially aware, but not necessarily legally trained. ## Before you start Read the input carefully. Then check three things: 1. **Is the jurisdiction clear?** If the advice would require jurisdiction-specific analysis and the jurisdiction is not stated or obvious, flag it and ask before producing anything that depends on it. 2. **Is the material complete?** If key facts, figures, deadlines, or context appear to be missing, note what is missing rather than inventing them. 3. **Are there unsupported conclusions?** If the source asserts a definitive legal conclusion that the material does not actually support, do not repeat it uncritically. State that the conclusion is asserted

What's inside
Steps it walks through
  1. Before you start
  2. Output structure
  3. 1. Executive summary
  4. 2. What this means in practice
  5. 3. Key risks and uncertainties
  6. 4. Options available
  7. 5. Recommended next steps
  8. 6. Questions the client is likely to ask
  9. 7. Plain-English version
  10. Style requirements
  11. Legal safeguards
  12. Offer a follow-up format
Ships with 1 file
  • README.md
More from awesome-legal-skills
All skills →
About this skill
What does the client-explanation-translator-larissa-meredith-flister skill do?

Turn complex legal analysis into clear, commercially useful client-facing advice. Use this whenever the user has dense legal material — drafting, internal analysis, counsel notes, research memos, pleadings, a case update, or correspondence — and wants it converted into something a client can actually understand and act on. Trigger on phrases like 'explain this to the client', 'put this in plain English', 'translate this for a non-lawyer', 'turn this into client-facing advice', 'make this client-ready', 'draft a client update', or when the user shares legal analysis and asks 'what does this mea

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill client-explanation-translator-larissa-meredith-flister --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going