LawDiver

View saved version →

---
name: caselaw-research
description: Search U.S. federal and state caselaw in LawDiver with a required jurisdiction, then summarize hits with real citations and good-law flags. Use when the user wants case research, case law search, or authorities on a legal issue. Do not use for non-legal web search, drafting filings, or inventing citations.
---

# Caselaw research (LawDiver)

Use LawDiver MCP tools only. Never invent case names, citations, holdings, or good-law status.

## When to use

- User asks to find cases on an issue, doctrine, or fact pattern
- User wants jurisdiction-scoped caselaw (state, circuit, SCOTUS, federal, etc.)
- User asks “what cases say about …” or “search caselaw for …”

## Steps

1. If jurisdiction is missing or ambiguous, ask once for the court scope (e.g. California state, Ninth Circuit, all federal). Do not run an unscoped national search.
2. Call `list_jurisdictions` only when the user needs help choosing a jurisdiction code.
3. Call `search_cases` with:
   - `query`: the user’s legal issue in plain language or keywords
   - `jurisdiction`: required object (`type`, plus `state` / `circuit` when needed)
   - `searchType`: `auto` unless the query is clearly a citation or case name
   - `limit`: 5–15 unless the user asks for more
4. Prefer search hit fields (name, citation, court, date, snippet, good-law flags). Do not treat search snippets as the full opinion.
5. If the user needs the full opinion text for a hit, call `retrieve_case` (if needed) then `get_opinion_text` with that `caseId`. Paginate with `nextOffset` until you have enough text.
6. Answer with cited authorities from tool results only. Flag negative treatment / not-good-law when tools report it.

## Do not

- Fabricate citations or quote language that did not come from LawDiver tools
- Use LawDiver for restaurants, news, or general web browsing
- Draft or e-file court documents
- Claim you deleted or edited anything in the corpus (tools are read-only)

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: check-citation-good-law
description: Verify U.S. case, statute, or specialty citations against the LawDiver corpus and report match status plus good-law / treatment signals when available. Use when the user asks if a cite is real, still good law, or overruled. Do not invent treatment signals.
---

# Check citations and good law (LawDiver)

Use LawDiver MCP tools only.

## When to use

- User asks whether a citation is real or in the corpus
- User asks if a case is still good law, overruled, or negatively treated
- User pastes cites to validate before relying on them

## Steps

1. Call `check_citation` with the citation string(s) the user provided.
2. Report match vs no-match clearly. For case hits, include good-law / treatment signals from the tool result when present.
3. If the user wants more on a matched case, call `retrieve_case` and/or `get_good_law` with the `caseId`.
4. For statute/rule or specialty hits that include `authorityKey`, use `retrieve_statute` when the user wants the section text.
5. If nothing matches, say so. Do not substitute a “similar” invented cite.

## Do not

- Invent Shepard’s-style treatment or claim a case is good law without tool support
- Pretend a no-match cite exists in LawDiver
- Delete, edit, or “fix” citations in any database (tools are read-only)

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: retrieve-opinion
description: Resolve a U.S. case citation or name in LawDiver and load the full opinion body text for quoting and pin cites. Use when the user wants the full case, opinion text, or quotes from a known citation. Do not use for free-form topic search (use caselaw-research) or non-legal lookups.
---

# Retrieve full opinion text (LawDiver)

Use LawDiver MCP tools only. Never invent opinion language.

## When to use

- User provides a reporter citation or case name and wants the opinion
- User asks for quotes, pin cites, or a summary of a specific case’s reasoning
- Prior search returned a `caseId` and the user needs the full body

## Steps

1. Call `retrieve_case` with `query` set to the citation or case name.
2. If the result is ambiguous (did-you-mean list), present candidates and confirm before continuing — or call again with the chosen `caseId`.
3. Call `get_opinion_text` with the confirmed `caseId`.
4. If `truncated` is true, call again with `offset` / `nextOffset` until you have the needed passages (or the full body).
5. Quote only text returned by `get_opinion_text`. Prefer that tool over PDFs or search excerpts.
6. Optionally call `get_good_law` or rely on treatment fields from prior tools when the user asks whether the case is still good law.

## Do not

- Invent pin cites or quote language not present in the returned body
- Treat search `includeOpinionText` excerpts as a substitute for `get_opinion_text`
- Claim the full opinion was retrieved if the body is still truncated and you stopped early without saying so

Referenced files: 1 — file references are metadata, not package contents.

View saved version →

---
name: retrieve-statute
description: Retrieve full U.S. statute, regulation, or court-rule section text from LawDiver by Bluebook citation or authority key. Use when the user asks for the text of a code section, regulation, or court rule. Do not use for caselaw search or inventing statutory language.
---

# Retrieve statute / rule text (LawDiver)

Use LawDiver MCP tools only. Never invent statutory wording.

## When to use

- User asks for the text of a statute, regulation, or court rule (e.g. `42 U.S.C. § 1983`)
- User has an `authorityKey` from `check_citation` and wants the section body

## Steps

1. Call `retrieve_statute` with a Bluebook-style citation that includes a section number, or with `authorityKey` from a prior `check_citation` hit.
2. If the citation is incomplete (missing section), ask for the section number before calling.
3. Return the section body and identifying metadata from the tool. If truncated, follow any pagination fields the tool returns.
4. If the lookup fails, say the section was not found in LawDiver. Do not paste a guessed version of the statute.

## Do not

- Fabricate statutory text
- Use this skill for case opinions (use retrieve-opinion)
- Claim LawDiver covers every jurisdiction’s entire code if a lookup misses

Referenced files: 1 — file references are metadata, not package contents.