Official launch partners
Chapter 1 · How can AI help my practice and day-to-day work?
00 Introduction 3 lessons
  1. 0.1 Who this guide is for and how to read it
  2. 0.2 The eight questions every lawyer asks
  3. 0.3 Survival glossary
01 How can AI help my practice and day-to-day work? 5 lessons
  1. 1.1 What is AI really?
  2. 1.2 Chat vs. agent
  3. 1.3 Where skills, MCP and plugins fit in
  4. 1.4 What lawyers are actually using AI for right now
  5. 1.5 Does it really save time?
02 Can I trust it? 5 lessons
  1. 2.1 Hallucinations
  2. 2.2 What is the answer based on?
  3. 2.3 When the model tells you what you want to hear
  4. 2.4 What a benchmark score really tells you
  5. 2.5 Test it on your own matters
03 Am I allowed to use it? 7 lessons
  1. 3.1 The three questions behind the question
  2. 3.2 What happens to the documents I upload?
  3. 3.3 Who can access, store or reuse my data?
  4. 3.4 Anonymisation and pseudonymisation
  5. 3.5 Professional rules by jurisdiction
  6. 3.6 Sovereignty and compliance
  7. 3.7 Other risks
04 How do I choose the best tools? 6 lessons
  1. 4.1 Same brain, different bodies
  2. 4.2 Subscription vs. API access
  3. 4.3 Legal AI tool or general-purpose assistant?
  4. 4.4 Open-source vs. closed, from the buyer's seat
  5. 4.5 Panorama of tools
  6. 4.6 Questions to ask before choosing a legal AI tool
05 How do we make it work across the firm or legal team? 7 lessons
  1. 5.1 Why one enthusiast is not an adoption strategy
  2. 5.2 Choosing a first pilot
  3. 5.3 Training the team
  4. 5.4 Measuring time saved and quality
  5. 5.5 Who maintains the tools and the shared know-how?
  6. 5.6 Change management
  7. 5.7 Working with IT, security and procurement
06 How do I get better results? 3 lessons
  1. 6.1 Give it better context
  2. 6.2 Turning your methods into reusable instructions
  3. 6.3 Watch out for AI slop
07 What does this mean for my career and my firm? 4 lessons
  1. 7.1 Which skills should lawyers develop?
  2. 7.2 What does a legal engineer do?
  3. 7.3 How AI may change fees, staffing and client expectations
  4. 7.4 What an AI-native firm might look like
08 Where and how do I start now? 4 lessons
  1. 8.1 Starter kits by profile
  2. 8.2 Classic mistakes to avoid
  3. 8.3 Section 1 recap
  4. 8.4 Staying current without drowning

Lesson 1.3 How can AI help my practice and day-to-day work? 7 min read

Your Methods, Your Tools (Skills, MCP and Plugins)

Plugin · Contracts team

Ask a general AI assistant to review an NDA from Acme against your firm's position, and it runs into two walls. First, it doesn't know your position: which clauses you push back on, which you accept, how you set out your comments. So it falls back on a generic checklist. Second, it can't open the NDA if the file sits in your document system, because it has no way in.

So you download the file, paste it in and type out your position. Then you do it again for the next NDA.

Three add-ons remove those walls. A skill gives the assistant your method. An MCP connection gives it access to a tool or a source. A plugin packages both so a whole team can install them in one step. You don't need to build any of them to use AI well. But they show up in product settings and vendor pitches, and they explain much of what a legal AI tool can actually do with your work.

Skills: your method, written down once

Skills give models domain-specific expertise. A is a folder with a text file inside. The file starts with a name and a one-line description of when to use it. Below that come the instructions, in plain language: the steps, the checks, the shape of the result.

The folder can also hold a template, your playbook, examples of good work, or a small program the assistant runs for a step that must be exact, such as counting days to a court deadline.

Anthropic introduced the format in October 2025 and published it as an open standard in December. It now works well beyond Claude: ChatGPT, GitHub Copilot, Google's Gemini CLI and Mistral's coding assistant read the same kind of folder Agent Skills Overview (opens in a new tab).

Inside a skill

nda-review/SKILL.md

name: nda-review

description: Review an NDA against our position. Use for any NDA or confidentiality agreement.

  1. Check term, scope and carve-outs.
  2. Flag any non-solicit.
  3. Compare each clause with playbook.md.
  4. Answer in our comment table.

The assistant always sees the name and description. It reads the steps only when a task matches.

What makes skills practical is when they load. The assistant doesn't read every skill all the time. At the start of a conversation it sees only each skill's name and description, about 100 tokens each. When your request matches a description, it opens that one skill and reads the full instructions Anthropic Agent Skills docs (opens in a new tab). So a team can install dozens of skills without filling the context window.

Try it

Which skill does it open?

Pick a request

  • nda-review opened · ~1,900 tokens

    Review an NDA against our position. Use for any NDA or confidentiality agreement.

    1. Check term, scope and carve-outs.
    2. Flag any non-solicit.
    3. Compare each clause with playbook.md.
    4. Answer in our comment table.
  • client-letter ~100 tokens

    Write to clients in our house style. Use when drafting a letter or email to a client.

  • court-deadlines ~100 tokens

    Count court deadlines from a date. Use when asked when something is due.

  • dd-checklist ~100 tokens

    Run our due diligence checklist on a data room. Use for M&A or financing diligence.

In context now
~2,200
If all four loaded
~7,500

Four skills installed. Only the one the task needs is read in full.

Illustrative skills. Token counts follow Anthropic's guidance: about 100 per name and description, under 5,000 per skill.

A skill has no set size. It can be one sentence: “When you write to a client, sign off with the matter number.” It can also run past a thousand lines, with every clause of your NDA position and the reasoning behind it. Both are real skills.

Long skills work because the same rule applies inside the folder. Anthropic advises keeping the main file under 500 lines and moving the detail into separate files that the main file points to Anthropic Skill authoring best practices (opens in a new tab). The assistant opens those files only when a step needs them, and it runs a program without reading it, so only the result enters the conversation. A long playbook takes no room in the conversation until a task needs it.

Example

One skill, one folder.

nda-review/

  • SKILL.md When the task matches The method: when to use it, the steps, the shape of the answer. · When the task matches
  • playbook.md When a step needs it Your position, clause by clause, with fallback wording. · When a step needs it
  • reference/standard-nda.pdf When a step needs it The firm's own NDA, the baseline for every comparison. · When a step needs it
  • reference/personal-data.md When a step needs it Extra checks, only for NDAs that cover personal data. · When a step needs it
  • examples/acme-review-2025.docx When a step needs it A past review the partner signed off. · When a step needs it
  • templates/comment-table.docx When a step needs it The table the answer goes in. · When a step needs it
  • scripts/check_defined_terms.py Run, not read Lists terms the NDA uses but never defines. · Run, not read

Only SKILL.md is required. Everything else stays closed until a step calls for it.

A skill is not the same as a prompt. A prompt is what you type in one conversation. It works for one task. When the conversation ends, the prompt is gone, and next time you must type it again. A skill stays saved. The model loads it only when the task needs it, with its files. You write the guidance one time and don't repeat it in each conversation.

Standing instructions, such as a project's custom instructions, are saved too, but they apply to every message whether they are relevant or not. Chapter 6 shows how to turn your own methods into skills.

One caution. A skill can tell the assistant to do anything the assistant is allowed to do, including run the programs inside it. Anthropic's own advice is to use skills only from sources you trust and to read every file before installing one. A skill is plain text, so you can read it, and you should.

MCP: one plug for many tools

Lesson 1.2 showed that an agent can only act through the tools its gives it. Until recently, every AI product had to build its own link to every outside service: one for Outlook, another for a document system, another for a case-law database. Each pairing was a separate project, so most were never built.

The is a shared standard for those links. A service builds one MCP connection, and every assistant that speaks MCP can use it.

Try it

Why one shared standard matters.

12 connections to build and keep working 3 assistants × 4 tools. Each new tool means 3 more.

Each tool builds one MCP connection. Every assistant that speaks MCP can use it.

Anthropic released MCP in November 2024. Within a year it had been adopted by ChatGPT, Gemini, Microsoft Copilot and others, and counted more than 10,000 public connections. In December 2025 Anthropic handed it to a foundation run under the Linux Foundation, a non-profit, so no single company controls it Anthropic Donating MCP, Dec 2025 (opens in a new tab).

In products you rarely see the letters MCP. Claude and Le Chat call these links connectors; ChatGPT calls them apps. Legal software is arriving fast. In May 2026, Anthropic announced more than 20 connectors for legal work, including the document systems iManage and NetDocuments, the e-discovery platforms Relativity and Everlaw, DocuSign, and Thomson Reuters LawSites May 2026 (opens in a new tab). Lawve, which publishes this guide, was one of them Anthropic Claude directory (opens in a new tab).

OpenAI followed in September with Astra for Law, a version of its GPT-6 Astra model set up for legal work, with its own legal search index. It came with 26 legal plugins from vendors such as Thomson Reuters, Harvey and iManage, 9 built by lawyers and legal engineers, and 47 skills LawSites Sep 2026 (opens in a new tab). Lawve is one of those plugins too OpenAI Lawve plugin (opens in a new tab).

Each connection is a door, so the three questions from lesson 1.2 apply: what it lets the assistant see, change and send. Well-built connections use your own access rights: if you can't open a matter in the document system, neither can the assistant.

Two more points. What the assistant reads through a connection goes to the model's provider, like anything you type, so the confidentiality rules in Chapter 3 apply. And text that comes in through a connection, such as an email or a document from the other side, can contain hidden instructions. That risk, prompt injection, is also covered in Chapter 3.

Plugins: the package a team installs

Skills and connections work on their own. A bundles several of them, often with ready-made commands, so they install in one step and everyone gets the same setup. A contracts plugin might bring a skill for NDAs, a skill for vendor agreements, the connection to your document system and a command that starts a review.

The idea is spreading across products. OpenAI describes a plugin as “a reusable package for a workflow that can include skills, apps, or both”, and is moving custom GPTs into plugins OpenAI Migrating custom GPTs (opens in a new tab).

Plugins are also how legal AI made the financial news this year. In early February 2026, Anthropic released a legal plugin for Claude Cowork, its desktop agent, covering contract review, NDA triage and compliance work, set up around an organisation's own playbook. On 3 February, shares in RELX, Wolters Kluwer and Thomson Reuters, the groups behind LexisNexis, Kluwer and Westlaw, fell by between 10% and 14% Canadian Lawyer Feb 2026 (opens in a new tab).

The plugin itself was mostly instructions written in plain language, plus connections. That is the lesson for buyers: much of what makes an AI tool “legal” is skills and connections around a general model. In May, Anthropic followed with 12 plugins for areas such as commercial, employment, privacy, IP and litigation work, each starting with a setup interview about the team's playbook, escalation rules and house style. All twelve are published on Lawve, where you can see the skills and commands each one bundles before you install it. Chapter 4 looks at what that means when you choose between a legal AI tool and a general assistant.

How the pieces fit

Back to the Acme NDA, with the contracts plugin installed. You type “Review the Acme NDA against our position.” The assistant matches the request to the NDA skill and reads your checklist. It uses the document system connection to find and open the file. The model then does what lesson 1.1 described: it reads, compares and writes, in the format your skill asks for. You review the result.

The skill supplied the method, the connection supplied the file, the plugin delivered both, and the model did the reading and writing.

In practice

Method, access, package.

Skill

Gives it
Your method
What it is
A folder of plain-text instructions, sometimes with templates or small programs
Example
How your team reviews an NDA
Before you install
Read it. Who wrote it, and what does it tell the assistant to do?

MCP connection

Gives it
Access to a tool or a source
What it is
A link built once by the service, usable by any assistant that speaks MCP
Example
Opening files in your document system
Before you install
What can it see, change and send? Whose access rights does it use?

Plugin

Gives it
One setup for the whole team
What it is
A bundle of skills, connections and commands, installed in one step
Example
A contracts plugin for the commercial team
Before you install
What is inside, and who keeps it up to date?

The model stays the same. These three decide what it knows about your work and what it can reach.

What this means for your work

  • You don't have to build anything to benefit. Many tools already ship with skills and connections. Ask which ones, who wrote them and who keeps them current.
  • Your know-how can become something the team installs. A checklist that lives in a partner's head or an old Word file can become a skill everyone uses the same way. Chapter 5 covers who should maintain it; Chapter 6 shows how to write it.
  • Treat each add-on like software. Read the skills, check what each connection can see, change and send, and know what a plugin bundles before you install it.

Next, lesson 1.4 turns from how these tools work to what lawyers are actually using them for, with the figures from recent surveys.