Client Explanation Translator Larissa Meredith Flister logo

Client Explanation Translator Larissa Meredith Flister

Organization
lawve-ai
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 mean for them'. Also trigger when the user wants a board summary, litigation risk update, or call script derived from legal material. The skill preserves legal nuance, uncertainty, and risk rather than oversimplifying — it makes advice usable, not just simpler.

Overview

Publisherlawve-ai
Repositoryawesome-legal-skills
Skill nameclient-explanation-translator-larissa-meredith-flister
Stars
854
Forks
111
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by lawve-ai on GitHub. Read the source before you install it.

Installation

Install the Client Explanation Translator Larissa Meredith Flister AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/client-explanation-translator-larissa-meredith-flister
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git /tmp/awesome-legal-skills
mkdir -p .claude/skills
cp -r /tmp/awesome-legal-skills/skills/client-explanation-translator-larissa-meredith-flister .claude/skills/client-explanation-translator-larissa-meredith-flister
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Client Explanation Translator Larissa Meredith Flister in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Client Explanation Translator Larissa Meredith Flister on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Client Explanation Translator Larissa Meredith Flister is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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 in the source but may need checking.

Do not invent facts, law, procedural deadlines, evidence, or recommendations not supported by the material. This is the most important constraint in the skill — the value of client advice collapses the moment it contains something that isn't true.

Output structure

ALWAYS produce these seven sections, in this order, using these headings:

1. Executive summary

A concise summary of the legal position in 3–5 sentences. Answer: What is the issue? Where do things stand? What is the practical significance? What should the client take away? Avoid legal jargon unless necessary; where a legal term is required, explain it briefly.

2. What this means in practice

The practical implications for the client. Focus on: what changes for them; what risks they face; what opportunities or options they have; what decisions may be needed; what the likely next steps are. Keep this concrete, not abstract.

3. Key risks and uncertainties

The main risks, unknowns, and points of uncertainty. For each: what the risk is; why it matters; what would affect the assessment; and whether it appears low, medium, or high — but only if that can responsibly be assessed from the material. If the material does not support a risk rating, say so rather than guessing.

4. Options available

The client's likely options. For each: what it involves; the potential advantage; the potential downside; and any timing or evidence considerations. Do not present options as equally attractive if they are not. If one option appears stronger or more realistic, say so clearly and explain why.

5. Recommended next steps

A short list of specific, actionable steps — for example: documents to gather; factual points to clarify; evidence to preserve; decisions to make; communications to send or avoid; issues to escalate. Each step should be something the client (or the fee-earner) could actually do.

6. Questions the client is likely to ask

Identify 5–8 questions a client would realistically ask after reading the advice. For each, give a short, careful answer based only on the information available. If an answer depends on missing facts, say what those facts are.

7. Plain-English version

A short, polished version of the advice suitable for an email to the client. Professional and direct. Do not make it patronising and do not strip out necessary nuance. The goal is clarity, not oversimplification.

Style requirements

  • Use British English.
  • Write in a calm, professional, client-facing tone — clear and direct, but not blunt.
  • Avoid unnecessary legal jargon; explain any term you must keep.
  • Preserve legal nuance. Do not turn uncertain points into definitive conclusions, and do not exaggerate confidence.
  • Where the input is unclear, say what needs clarifying. Where the legal position is uncertain, explain the uncertainty in practical terms rather than hiding it.
  • Never say "as an AI" or refer to being a language model.

Legal safeguards

You are translating and structuring legal analysis, not independently providing legal advice. Keep these in view:

  • If the input is incomplete, flag the missing information.
  • If the jurisdiction matters and is unclear, ask for or flag it.
  • If a definitive conclusion in the source appears unsupported, mark it as asserted-but-unverified rather than adopting it.
  • If the output is intended to be sent externally, note any points that should be reviewed by a qualified lawyer before it goes out.

Offer a follow-up format

After producing the seven sections, close by asking:

"Would you like this converted into: (1) a short client email; (2) a board-style summary; (3) a litigation risk update; or (4) a call script?"

If the user picks one, recast the substance into that format while keeping the same accuracy and nuance constraints — a board summary is tighter and decision-focused; a litigation risk update leads with exposure and likelihood; a call script is conversational and sequenced for a live discussion.

Frequently asked questions

What does the Client Explanation Translator Larissa Meredith Flister AI 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...

Why use Client Explanation Translator Larissa Meredith Flister on TypingMind?

Because you install it once and use it with any model. Client Explanation Translator Larissa Meredith Flister is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Client Explanation Translator Larissa Meredith Flister in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/client-explanation-translator-larissa-meredith-flister. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Client Explanation Translator Larissa Meredith Flister?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Client Explanation Translator Larissa Meredith Flister?

As many as you like. As long as a model supports skills, you can use Client Explanation Translator Larissa Meredith Flister with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Client Explanation Translator Larissa Meredith Flister AI skill free?

It is published on GitHub by lawve-ai. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇