Disputes And Legal Holds logo

Disputes And Legal Holds

CommunityPopular
cbrock84
disputes-and-legal-holds

Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automatic deletion across every system that holds relevant material, preserving privilege, managing outside counsel and cost, and evaluating settlement against the real cost of continuing. Use this to respond to a claim or demand letter, issue a hold, work out which systems the hold has to reach, or decide whether to fight.

Overview

Publishercbrock84
Repositoryheadcount
Skill namedisputes-and-legal-holds
Stars
2K
Forks
316
Bundled files
1
LicenseMIT
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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cbrock84 on GitHub. Read the source before you install it.

Installation

Install the Disputes And Legal Holds 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/cbrock84/headcount/tree/main/plugins/legal-risk/skills/disputes-and-legal-holds
  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/cbrock84/headcount.git /tmp/headcount
mkdir -p .claude/skills
cp -r /tmp/headcount/plugins/legal-risk/skills/disputes-and-legal-holds .claude/skills/disputes-and-legal-holds
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Disputes And Legal Holds 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 Disputes And Legal Holds 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 Disputes And Legal Holds 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.

Disputes and legal holds

The decisions that determine how a dispute goes are made in the first week, usually by people who do not know a dispute has started.

This structures the operational response. Procedural obligations and their deadlines vary by jurisdiction and forum — get counsel engaged early, and let them drive strategy.

Preservation attaches earlier than most people expect

The obligation to preserve begins when litigation is reasonably anticipated — which can be a demand letter, a threat made in a meeting, a regulator's inquiry, or an internal complaint serious enough that a claim is foreseeable. It does not wait for a filing.

Destruction after that point is treated far more seriously than the underlying dispute. Routine automatic deletion continuing through a hold is the common version, and "it was our normal policy" is not the defense people assume.

Issue the hold in writing, and make it reach the systems

A hold has two halves and organizations routinely do only the first.

  • Notify the people. Written, naming the matter in general terms, describing the categories of material to preserve, instructing recipients not to delete and not to discuss, and requiring acknowledgment. Identify custodians by what they touched, not by seniority.
  • Suspend the machinery. Automatic deletion runs on schedules nobody remembers setting: mail retention, chat history expiry, ticket archival, log rotation, backup rotation, CRM purges, device wipe on offboarding. Each needs an explicit suspension for the affected scope.

The systems half is where holds fail, because the notice goes out and everyone assumes it was sufficient. Keep a list of every system with an automatic deletion schedule so that the question is answerable in an afternoon rather than a fortnight.

Maintain the hold as a live thing

Re-notify periodically, add custodians as the matter develops, and cover departures — an employee leaving under a hold means their mailbox, files and device do not follow the standard offboarding path. Release the hold in writing when counsel says so, and only then.

Privilege is easy to lose and cannot be recovered

Privilege protects legal advice, not facts and not business decisions dressed as legal ones. Copying a lawyer onto a business discussion does not make it privileged; forwarding privileged advice widely inside the organization can waive it.

Where an investigation is being run for the purpose of legal advice, structure it that way from the start — directed by counsel, marked, and circulated narrowly. Retrofitting privilege afterward generally fails.

Manage counsel and cost deliberately

Agree scope, staffing, rates and a budget with checkpoints before work starts, and require early written assessment of the realistic range of outcomes. Discovery is usually the largest cost and the most controllable one — narrowing custodians and date ranges early matters more than any hourly rate negotiation.

Decide about settlement on expected cost, not on principle

Compare the realistic range of outcomes, weighted, against the full cost of continuing: fees, management time, disruption, disclosure risk, and the effect on other matters. Management time is the cost most consistently omitted and is often the largest.

Consider what a settlement signals to other potential claimants, and get releases that are broad enough to actually end it.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Wait for a filing before preserving.
  • Send a hold notice without suspending the automatic deletion it depends on.
  • Offboard someone under a hold through the standard process.
  • Assume copying counsel on a message makes it privileged.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Disputes And Legal Holds AI skill do?

Handles a dispute from the first sign of it — recognizing when preservation obligations attach, issuing and scoping a legal hold, suspending automatic deletion across every system that holds relevant material, preserving privilege, managing outside counsel and cost, and evaluating settlement against the real cost of continuing. Use this to respond to a claim or demand letter, issue a hold, work out which systems the hold has to reach, or decide whether to fight.

Why use Disputes And Legal Holds on TypingMind?

Because you install it once and use it with any model. Disputes And Legal Holds 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 Disputes And Legal Holds in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cbrock84/headcount/tree/main/plugins/legal-risk/skills/disputes-and-legal-holds. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Disputes And Legal Holds?

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 Disputes And Legal Holds?

As many as you like. As long as a model supports skills, you can use Disputes And Legal Holds with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Disputes And Legal Holds AI skill free?

Yes. It is published on GitHub by cbrock84 under the MIT license. 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 👇