Witness
ruvnet/ruflo
Sign, verify, and track fix-marker regressions over time using a deterministic Ed25519 witness manifest.
Build a deposition outline for a witness — pull their documents from the eDiscovery platform, organize topics around the case theory, and surface impeachment material.
$ npx skills add anthropics/claude-for-legal --skill deposition-prep -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install anthropics/claude-for-legal deposition-prep --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/litigation-legal/skills/deposition-prep .claude/skills/deposition-prep && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deposition-prep" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/litigation-legal/skills/deposition-prep into .claude/skills/deposition-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deposition-prep", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/anthropics/claude-for-legal/tree/main/litigation-legal/skills/deposition-prepType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add anthropics/claude-for-legal --skill deposition-prep -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install anthropics/claude-for-legal deposition-prep --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .agents/skills && cp -r skills-src/litigation-legal/skills/deposition-prep .agents/skills/deposition-prep && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deposition-prep" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/litigation-legal/skills/deposition-prep into .agents/skills/deposition-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deposition-prep", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add anthropics/claude-for-legal --skill deposition-prep -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install anthropics/claude-for-legal deposition-prep --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/litigation-legal/skills/deposition-prep .cursor/skills/deposition-prep && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deposition-prep" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/litigation-legal/skills/deposition-prep into .cursor/skills/deposition-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deposition-prep", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/anthropics/claude-for-legal.git --path litigation-legal/skills/deposition-prep--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add anthropics/claude-for-legal --skill deposition-prep -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install anthropics/claude-for-legal deposition-prep --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/litigation-legal/skills/deposition-prep .gemini/skills/deposition-prep && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deposition-prep" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/litigation-legal/skills/deposition-prep into .gemini/skills/deposition-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deposition-prep", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install anthropics/claude-for-legal deposition-prepInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add anthropics/claude-for-legal --skill deposition-prep -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .github/skills && cp -r skills-src/litigation-legal/skills/deposition-prep .github/skills/deposition-prep && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deposition-prep" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/litigation-legal/skills/deposition-prep into .github/skills/deposition-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deposition-prep", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add anthropics/claude-for-legal --skill deposition-prep -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install anthropics/claude-for-legal deposition-prep --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/litigation-legal/skills/deposition-prep .opencode/skills/deposition-prep && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deposition-prep" agent skill from https://github.com/anthropics/claude-for-legal/tree/main/litigation-legal/skills/deposition-prep into .opencode/skills/deposition-prep/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deposition-prep", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
deposition-prepBuild a deposition outline for a witness — pull their documents from the eDiscovery platform, organize topics around the case theory, and surface impeachment material.
Deposition Prep is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Build a deposition outline for a witness — pull their documents from the eDiscovery platform, organize topics around the case theory, and surface impeachment material. Use when the user says "depo prep for [witness]", "build a depo outline", or "prepare for [name]'s deposition".
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A suite of plugins for legal workflows. The licence is Apache-2.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4a6c651. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Deposition Prep loads about 3.5k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 1,600 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from anthropics/claude-for-legal at commit 4a6c651, republished under its Apache-2.0 licence (© anthropics). 1,600 words, ~3,505 tokens.
.claude/skills/deposition-prep/SKILL.md (or your agent's skills folder).~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → case theory, key facts.If the user's jurisdiction includes England & Wales and they're asking for a trial witness statement for the Business & Property Courts (or any CPR-governed proceeding), PD 57AC applies. The statement must be in the witness's own words, must not contain argument, must identify the documents the witness used to refresh their memory, and must carry the required confirmation of compliance and the legal representative's certificate.
Drafting a narrative "as the witness" from a chronology, document set, or your account of the case is exactly what PD 57AC was designed to prevent. Courts are actively sanctioning AI-assisted witness statement drafting. If you ask me to do it, I won't.
What I WILL do: prepare question prompts to elicit the witness's actual recollection; capture and organize what the witness says (their words, not mine); generate the list of documents they were shown; run a PD 57AC compliance checklist against a statement they've drafted; draft the solicitor's certificate of compliance. I help you get the witness's evidence into the statement. I don't write the evidence.
For US depositions, declarations, and affidavits: different rules, but the same discipline applies. A declaration in the declarant's voice that the declarant didn't write is a credibility problem at best.
Before producing output, check where it's going. If the user has named a destination (a channel, a distribution list, a counterparty, "everyone"), ask whether it's inside the privilege circle. Public channels, company-wide lists, counterparty/opposing counsel, vendors, and clients (for work product) waive the protection. When the destination looks outside the circle, flag it and offer (a) the privileged version for legal only, (b) a sanitized version for the broader channel, or (c) both — don't silently apply a privileged header and then help paste it somewhere the header won't protect it. See the canonical ## Shared guardrails → Destination check in this plugin's CLAUDE.md.
A depo outline is a map: background → lock in the good facts → confront with the bad ones → box in on the theory. This skill builds the map from the documents and the case theory.
Two rules that govern every citation and every quotation pulled from the record into this outline. Canonical statement lives in the plugin's CLAUDE.md shared guardrails; repeated here because an impeachment confrontation built on a misquoted prior statement or a misgrounded transcript cite collapses the impeachment.
Verbatim quotes from the record must be verbatim. Never put quotation marks around words attributed to opposing counsel, the witness, another deponent, the court, or any record document unless you have the exact passage in front of you and can cite to it. When you want to characterize what someone said but can't find the exact words:
[verify against record — Tr. p. __]."[verify exact quote — record cite pending][verify exact quote] must be flagged in the reviewer note.Pinpoint cites must support the whole proposition. If an impeachment point is "the witness said X, Y, and Z on [date]," verify the pinpoint cite supports X AND Y AND Z. If it only supports Z, split the cite — "said X (Tr. p. 10), Y (Tr. p. 12), Z (Tr. p. 15)" — or narrow the proposition. A cite that supports part of an impeachment is the failure mode where opposing counsel asks the witness to read more of the surrounding transcript and your confrontation falls apart.
A depo outline is read aloud in real time. That's oral advocacy, not written. It means:
"Too thorough" for oral work reads as unfocused. If the outline is long because the record is deep, say so and flag where the lawyer should collapse.
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → case theory (theory, pivot fact, key facts for/against), eDiscovery platform.
Conflicts gate — unbypassable. Before building an outline, check ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml for the matter slug. If the matter is not in _log.yaml, refuse and route:
"I don't see [matter slug] in the matter log. Run
/litigation-legal:matter-intakefirst so the conflicts check runs and the matter workspace is set up. I won't build a deposition outline on a matter that hasn't been intaken — the conflicts check is the gate."
Do not proceed on an unintaken matter. Intake is what runs conflicts and writes the _log.yaml row this skill reads from.
The "why" connects to the theory. If the witness can establish the pivot fact, that's the centerpiece of the outline.
Prep structure differs by posture. Identify the witness posture before writing a single question:
Research the applicable deposition rules for the forum and witness type (FRCP 30 / state equivalent, local rules, judge's standing orders on depositions). Cite primary sources. Don't apply a one-size prep structure — the question form, the approach to documents, and the use of impeachment material all depend on posture.
No silent supplement. If a research query to the configured legal research tool (Westlaw, CourtListener, Trellis, Descrybe, or firm platform) returns few or no results for the forum's deposition rules or a cite you need for impeachment, report what was found and stop. Do NOT fill the gap from web search or model knowledge without asking. Say: "The search returned [N] results from [tool]. Coverage appears thin for [rule / authority]. Options: (1) broaden the search query, (2) try a different research tool, (3) search the web — results will be tagged [web search — verify] and should be checked against a primary source before relying, or (4) leave the [UNCERTAIN] marker and stop here. Which would you like?" A lawyer decides whether to accept lower-confidence sources; the skill does not decide for them.
Source attribution. Tag every rule reference, case cite, and authority in the outline with where it came from: [Westlaw], [CourtListener], [Trellis], [Descrybe], or the MCP tool name for citations retrieved from a legal research connector; [web search — verify] for web-search citations; [model knowledge — verify] for citations recalled from training data; [user provided] for citations the partner or senior associate supplied. Document citations (Bates, production numbers) retain their native source. Citations tagged verify carry higher fabrication risk and should be checked before the deposition. Never strip or collapse the tags.
From the eDiscovery platform (Everlaw/Relativity/DISCO if connected):
Organize by date. Flag the hot docs — the ones that matter most for the theory.
Each topic is a thing you want to establish or explore. Organize around the theory:
Background (always first — lock in uncontroversial facts before the witness is defensive):
Good facts (lock them in before confronting):
~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → key facts for us, that this witness can establishBad facts (confront with documents):
Impeachment (if hostile or if they contradict):
The pivot fact:
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
# Deposition Outline: [Witness Name]
**Date:** [depo date]
**Witness role:** [title, relationship to case]
**Witness posture:** [adverse / friendly / neutral / 30(b)(6) or state equivalent] — drives question form
**Applicable deposition rules:** [FRCP 30 / state rule / local rule / standing order — with pinpoint cites] `[UNCERTAIN — verify currency]`
**Why we're taking this depo:** [one sentence — the goal]
**Theory connection:** [how this witness fits the case theory]
---
## I. Background
[Questions — closed, one fact each. Lock in the uncontroversial stuff.]
## II. [Good fact topic]
**Goal:** Establish [fact] for use at summary judgment / trial.
**Documents:**
- [Bates] — [description] — [why it matters]
**Questions:**
[The sequence. Each question closed. Build to the admission.]
## III. [Bad fact topic]
**Goal:** Get the witness's explanation of [bad fact] on our terms before they're prepped for trial.
[Same structure]
## IV. Impeachment material (use if needed)
[Prior statements / documents to confront with, if the witness contradicts]
## V. [Pivot fact sequence]
**Goal:** [The thing the case turns on]
[This is the tightest section. Every question is a yes/no. Every question establishes one fact. Build the box.]
---
## Exhibit list
| # | Bates | Description | Used in section |
|---|---|---|---|
## Marker discipline
Use inline while building and reviewing:
- `[VERIFY: factual assertion]` — any fact not confirmed against the record
- `[UNCERTAIN: legal proposition]` — any legal point (rule, deadline, scope-of-questioning limit) not confirmed against current authority
- `[CITE NEEDED: specific cite]` — record or authority cite pending
## Notes for the attorney
- [Anything the outline doesn't capture — witness demeanor notes, strategic calls to make in the moment]
---
**Privileged / work-product material.** This outline is built from case materials and work product and inherits their protection status. Keep it in the privileged-materials folder, mark it appropriately, and make any distribution decision (co-counsel, client, experts) deliberately — distribution outside the privilege circle can waive protection.
**Cite check any authority relied on.** Rule citations (FRCP 30, state equivalents, local rules, standing orders) and any case law pulled into the outline were generated by an AI model. Verify each against Westlaw, CourtListener, or your research platform — confirm currency and scope before using at the deposition. Source tags on each citation (e.g., `[Westlaw]`, `[web search — verify]`) show where the cite came from; `verify` tags carry higher fabrication risk and should be checked first.© anthropics, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in litigation-legal/skills/deposition-prep of anthropics/claude-for-legal.
Open the folder on GitHubat commit 4a6c651
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in anthropics/claude-for-legal, which our catalogue first saw on October 7, 2026.
Deposition Prep next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deposition Prep this skillanthropics/claude-for-legal | 9.6k | 1 repos | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Witnessruvnet/ruflo | 74k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Deadline Prepdavila7/claude-code-templates | 32k | — | ~739 | Automated safety check: Pass | MIT | |
| Interview PrepRightNow-AI/openfang | 18k | — | ~973 | Automated safety check: Pass | Apache-2.0 | |
| Outlines Structured GenerationOrchestra-Research/AI-Research-SKILLs | 13k | 9 repos | ~4k | Automated safety check: Pass | MIT | |
| Wit AI AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~727 | Automated safety check: Pass | None |
ruvnet/ruflo
Sign, verify, and track fix-marker regressions over time using a deterministic Ed25519 witness manifest.
davila7/claude-code-templates
Generate a structured demo outline from your session's change log and git history.
RightNow-AI/openfang
Technical interview preparation expert for algorithms, system design, and behavioral questions
Orchestra-Research/AI-Research-SKILLs
Uses the Outlines library to constrain model output to a JSON schema, Pydantic model, regex or fixed set of choices when running local models.
ComposioHQ/awesome-claude-skills
Automate Wit AI tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
ruvnet/ruflo
Verify witness chain integrity and detect provenance gaps. An agent skill from ruvnet/ruflo.
anthropics/claude-for-legal
Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.
anthropics/claude-for-legal
Holds student work in a queue for a legal clinic professor to approve, edit-then-approve or return before anything reaches clients or courts.
anthropics/claude-for-legal
Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.
anthropics/claude-for-legal
Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.
anthropics/claude-for-legal
Searches watched registries for community legal skills, shows matches with descriptions and offers the full SKILL.md before anything is installed.
anthropics/claude-for-legal
Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.
Build a deposition outline for a witness — pull their documents from the eDiscovery platform, organize topics around the case theory, and surface impeachment material. Deposition Prep is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Build a deposition outline for a witness — pull their documents from the eDiscovery platform, organize topics around the case theory, and surface impeachment material.
Deposition Prep fits situations like: the user says depo prep for [witness]; build a depo outline; prepare for [name]s deposition.
Run `npx skills add anthropics/claude-for-legal --skill deposition-prep -a claude-code`. Or copy the skill folder (litigation-legal/skills/deposition-prep in anthropics/claude-for-legal) into .claude/skills/deposition-prep in your project. Claude Code loads it when a task matches its description.
Run `npx skills add anthropics/claude-for-legal --skill deposition-prep -a codex`. Or copy the skill folder (litigation-legal/skills/deposition-prep in anthropics/claude-for-legal) into .agents/skills/deposition-prep in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add anthropics/claude-for-legal --skill deposition-prep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deposition-prep, .gemini/skills/deposition-prep, .github/skills/deposition-prep and .opencode/skills/deposition-prep in your project.
SKILL.md names no scripts, command-line tools or credentials: Deposition Prep is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Deposition Prep is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Deposition Prep: Witness (ruvnet/ruflo, 74k stars), Deadline Prep (davila7/claude-code-templates, 32k stars), Interview Prep (RightNow-AI/openfang, 18k stars) and Outlines Structured Generation (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,629 GitHub stars. The repository holds 147 skills in this directory. The repository was last updated on September 29, 2026.
Source: anthropics/claude-for-legal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.