New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Subpoena Triage

by anthropics in anthropics/claude-for-legal

Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar.

OfficialApache-2.0Auto-check passed

Install Subpoena Triage

skills CLI
$ npx skills add anthropics/claude-for-legal --skill subpoena-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install anthropics/claude-for-legal subpoena-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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/subpoena-triage .claude/skills/subpoena-triage && rm -rf skills-src

Use ~/.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/

Facts

Skill name
subpoena-triage
GitHub stars
9.6k
Used in
1 other repo
Token cost
~4.5k tokens
SKILL.md length
1,683 words
Files
1
Skills in repo
147
Repo updated
First seen
Licence
Apache-2.0

At a glance

Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar.

  • Works in 10 steps: Research the applicable rule → Classify → Extract key fields → …
  • The user says we got a subpoena
  • SKILL.md covers Purpose, Jurisdiction assumption, Side context and Load context, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Subpoena Triage is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar. Use when the user says "we got a subpoena", "served with a subpoena", or shares a subpoena, CID, or third-party document request to evaluate.

Its SKILL.md is about 4.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.

When your agent uses it

  • The user says we got a subpoena
  • Served with a subpoena
  • Shares a subpoena
  • Third-party document request to evaluate

Example prompts

  • “we got a subpoena”
  • “served with a subpoena”
  • “/subpoena-triage”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Research the applicable rule
  2. Classify
  3. Extract key fields
  4. Portfolio cross-check
  5. Analyze scope, burden, privilege
  6. Objections framework
  7. Compliance plan
  8. Deadlines
  9. Write triage
  10. Hand off

What it can do on your machine

Read from SKILL.md and the folder at commit 4a6c651. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Subpoena Triage loads about 4.5k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 1,683 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from anthropics/claude-for-legal at commit 4a6c651, republished under its Apache-2.0 licence (© anthropics). 1,683 words, ~4,481 tokens.

Download SKILL.mdSave it as .claude/skills/subpoena-triage/SKILL.md (or your agent's skills folder).
name
subpoena-triage
description
Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar. Use when the user says "we got a subpoena", "served with a subpoena", or shares a subpoena, CID, or third-party document request to evaluate.
argument-hint
[path-to-subpoena] [--slug=custom-slug]

/subpoena-triage

  1. Read the subpoena from provided path.
  2. Classify (third-party-docs / third-party-depo / party / CID / grand-jury).
  3. If grand jury → stop, escalate per ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md. Otherwise continue.
  4. Load ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml for cross-check. Load ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → landscape, privilege conventions, escalation norms.
  5. Follow the workflow and reference below.
  6. Extract key fields, analyze scope/burden/privilege, produce objections framework + compliance plan + deadline calendar.
  7. Write ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md. Copy or link subpoena to ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/incoming.[ext].
  8. Hand off: /legal-hold --issue if hold not in place; /matter-intake if materiality warrants; /matter-briefing [slug] if party subpoena in existing matter.

Subpoena Triage

Purpose

Subpoenas arrive with deadlines. The failure modes: missing the deadline, over-producing (privilege waiver, burden we should have objected to), under-producing (contempt exposure), or missing a motion-to-quash window. This skill classifies, analyzes, and produces a compliance plan with objections framework.

Jurisdiction assumption

The rule cited in Step 0 is the operative one for this subpoena in this forum. Subpoena practice varies materially: federal (FRCP 45) vs. state equivalents, state-to-state variants, local rules, court-specific standing orders, and the subpoena type (trial, deposition, document production) all change objection deadlines, place-of-compliance limits, privilege-log requirements, and cost-shifting. Every rule output here is a starting-point heuristic — confirm currency and the local variant before asserting in writing.

Side context

This skill is inherently defensive — a subpoena has been served on the recipient and the posture is respond/object/comply. Read ## Side in the practice profile. If the user's default side is plaintiff, note that receiving a subpoena is common for plaintiffs too (witness subpoenas, third-party requests directed at the plaintiff's own records) but the framing here is always "subpoena served on us, how do we respond." If the user is defense (typical), the framing aligns with the default. If the matter has a different posture than the default (e.g., defense practitioner receiving a subpoena in a matter where they're pro se for a family member), prompt the user to confirm posture before proceeding.

Load context

  • The subpoena document (user provides path or drops it in-session)
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/matters/_log.yaml — for related matter lookup and legal hold status
  • ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md → landscape (regulators we deal with), house privilege conventions, escalation norms

Workflow

Step 0: Research the applicable rule

Before analyzing this subpoena, research the applicable rule of civil procedure for the forum (FRCP 45 for federal, the state equivalent otherwise) and the subpoena type (trial, deposition, document production). Identify: place-of-compliance limits, objection deadlines (these often run from the EARLIER of the compliance date or a fixed number of days after service), privilege-log requirements, and who bears costs. Cite with pinpoint references. Verify currency — rules and local variants change. Flag grand-jury subpoenas for immediate criminal-counsel escalation.

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 rule, variant, or pinpoint, 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 / forum / variant]. 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) 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, statute, and regulation in the triage output 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 citations from web search; [model knowledge — verify] for citations recalled from training data; [user provided] for citations the user supplied (e.g., from the subpoena or prior matter work). Citations tagged verify carry higher fabrication risk and should be checked first. Never strip or collapse the tags — they are counsel's fastest signal about which citations to verify before asserting in objections or filings.

Step 1: Classify

Subpoenas come in flavors with different rules; confirm the specifics against the rule you just researched:

  • Third-party document subpoena (civil) — we're not a party to the litigation; someone wants our documents. Usual objection categories: relevance, burden, privilege, place-of-compliance / geographic reach.
  • Third-party deposition subpoena — someone wants an employee to testify. Scope, relevance, burden; possible motion to quash; witness prep required.
  • Party subpoena — we ARE a party; this is discovery in a litigation we're tracking. Treat as discovery, not inbound — it should map to an existing matter.
  • Regulatory civil investigative demand (CID) — FTC, SEC, DOJ, state AG. Different rules, different posture; often more deferential but also more consequential.
  • Grand jury subpoena — criminal. Escalate immediately to criminal counsel; different skill path (outside this skill's scope — flag for escalation).
Step 2: Extract key fields
  • Issuing authority — court (which), agency (which), counsel (if civil)
  • Issuing party — who requested (if civil)
  • Case / matter caption — the litigation we're being asked about
  • Document categories sought — numbered list
  • Testimony topics (if depo) — Rule 30(b)(6) designations
  • Deadline for response/objection — date served + computing the response window per applicable rule
  • Production date — date by which documents must be produced
  • Geographic scope — custodians, locations, systems implicated
  • Custodian of record designation — who at the company is the witness/signatory
Step 3: Portfolio cross-check
  • Party subpoena → related to existing matter: verify the caption matches a matter in _log.yaml. If yes, route to that matter's workflow; this triage is informational.
  • Third-party subpoena → caption we don't recognize: capture the parties; log as standalone inbound.
  • Multiple subpoenas from same case: flag coordinated issuance; a single response strategy may apply.
Step 4: Analyze scope, burden, privilege

Scope / relevance

  • Do the categories map to actual documents we plausibly have?
  • Is any category a fishing expedition (overbroad, untethered to claims/defenses of the underlying case)?
  • Place of compliance / geographic reach — apply the researched rule; limits differ by subpoena type (trial vs. document vs. deposition).

Burden

  • Custodians implicated, systems searched, time period
  • Estimated volume (rough: small / medium / large / extreme)
  • Cost — third-party responders may have cost-shifting available; check the researched rule.

Privilege

  • Attorney-client or work product likely implicated? (Almost always yes for anything legal-related; often yes for communications involving in-house or outside counsel.)
  • Other privileges — trade secret, HIPAA (if applicable), state privilege, common interest
  • Privilege log will be required — flag the format per ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md

Other objection grounds

  • Confidentiality — protective order needed?
  • Duplicative — do they already have this from another party?
  • Not possessed — we don't have what they're asking for (document with specificity)
  • Improperly served — check the researched rule's service requirements
Show full SKILL.md (610 more words)Show less
Step 5: Objections framework

Draft a structured objections outline — not the final objections letter, but the outline of what objections apply and why. The user (often with outside counsel) finalizes.

Each objection:

  • Legal basis — cite the pinpoint from the rule researched in Step 0
  • Specific application to this subpoena (which categories, which custodians)
  • Strength (strong / reasonable / weak)
Step 6: Compliance plan

Even when objecting, we often produce some of what's requested. Plan:

  • Scope of likely production — after objections, what we'd produce
  • Custodians to search — names and systems
  • Date range
  • Review protocol — who reviews for privilege (us, outside counsel, contract reviewers)
  • Production format — per the subpoena or per negotiated protocol (TIFF+load file, native, PDF)
  • Privilege log requirements — format, fields
Step 7: Deadlines

Use the deadlines identified in the Step 0 research. Note that objection deadlines often run from the EARLIER of the compliance date or a fixed number of days after service — do not default to a single number without checking the applicable rule and local variant.

  • Response deadline — per researched rule; note if user needs more time (meet-and-confer to extend is standard)
  • Objection deadline — per researched rule (federal / state rule + any local variant)
  • Production date — if no objections succeed
  • Motion to quash window — if pursuing that path, timing is critical

Calendar all of them. Immediate action item.

Step 8: Write triage

Output: ~/.claude/plugins/config/claude-for-legal/litigation-legal/inbound/[slug]/triage.md.

markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]

# Subpoena Triage

> **NOT A SUBSTITUTE FOR OUTSIDE COUNSEL.** This is a structured classification and scoping read to support fast decisions on deadlines, holds, and engagement. Every rule reference is a starting-point heuristic; jurisdiction-specific analysis, objections finalization, motions practice, and merit calls on privilege require licensed counsel familiar with the forum. Engage outside counsel for any subpoena above routine third-party document scope.

**Slug:** [slug]
**Served:** [YYYY-MM-DD]
**Served on:** [entity / registered agent]
**Incoming file:** [path]
**Classification:** [third-party-docs / third-party-depo / party / CID / grand-jury]

---

## Key fields

- **Issuing authority:** [court/agency]
- **Issuing party:** [name]
- **Case caption:** [caption]
- **Response deadline:** [date]
- **Production date:** [date]
- **Motion-to-quash window:** [date range]

## Categories sought (summary)

[numbered list, concise]

## Custodians / systems likely implicated

[list]

---

## Portfolio cross-check

**Related matter:** [slug or "none"]
**If party subpoena:** [routed to existing matter or new matter?]
**If third-party:** [standalone inbound]

---

## Scope & burden analysis

**Scope:** [relevance assessment by category]
**Burden estimate:** [small / medium / large / extreme — with reasoning]
**Geographic reach issues:** [any]

## Privilege analysis

*Privilege scoping is a first-pass read; final call is counsel's, not this skill's.*

**Attorney-client / work product likely implicated:** [yes/no + which categories] `[SME VERIFY]`
**Other privileges:** [trade secret, HIPAA, state, common interest] `[SME VERIFY]`
**Privilege log format required:** [per `~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md`]

---

## Objections framework

*Every row below requires `[SME VERIFY]` before asserting in writing — jurisdiction, rule currency, waiver risk.*

| Objection | Legal basis | Applies to | Strength | SME verified? |
|---|---|---|---|---|
| Relevance | [rule] | [categories] | [strong/reasonable/weak] | [ ] |
| Burden | [rule] | [categories] | | [ ] |
| Privilege | A/C, WP | [all producing docs] | strong (always) | [ ] |
| Duplicative | [rule/doctrine] | [if applicable] | | [ ] |
| [other] | | | | [ ] |

---

## Compliance plan (if responding)

- **Scope of likely production:** [after objections]
- **Custodians / systems:** [list]
- **Date range:** [range]
- **Review protocol:** [who, how]
- **Production format:** [format]
- **Privilege log:** [format, est. entries]

---

## Deadlines (calendar these)

*All deadlines below come from the Step 0 rule research. `[SME VERIFY]` confirms the rule, variant, and computation for this forum and this subpoena type — state variants and local rules differ.*

- **Response deadline:** [date] `[SME VERIFY]`
- **Objection deadline:** [date] — cite: [rule + pinpoint] `[SME VERIFY]`
- **Meet-and-confer by:** [date] (typically before objection deadline) `[SME VERIFY]`
- **Production date:** [date]

---

## Immediate actions

- [ ] Legal hold issued — [yes/no] — if no, run `/legal-hold [slug] --issue` with subpoena scope
- [ ] Outside counsel engaged — [yes/who/TBD]
- [ ] Meet-and-confer scheduled — [date]
- [ ] Matter created in log — [yes/no/TBD — usually yes for anything above the smallest third-party docs subpoena]
- [ ] Insurance / cost-shifting analysis — [if burden is large]
- [ ] Internal escalation — [who]

---

## Recommendation

[Two paragraphs: what to do. Objection posture. Production posture. Whether outside counsel handles objections or we do. Whether to move to quash.]

---

## Citation verification

Every rule reference, case, statute, and regulation in this triage — including the Step 0 research citations, objection bases, and the privilege-log format pointer — is AI-generated and unverified. Before relying on any cite (especially in objections, a motion to quash, or correspondence with the issuing party), run a verification pass against a legal research tool (Westlaw, CourtListener, Trellis, Descrybe, or your firm's platform) for accuracy, good law status, and local variants. Fabricated or misquoted citations in filed documents have resulted in sanctions. Source tags on each citation (e.g., `[Westlaw]`, `[web search — verify]`) show where it came from; `verify` tags carry higher fabrication risk and should be checked first.
Step 9: Hand off

Before responding to the subpoena (serving objections, producing documents, appearing for deposition, or filing a motion to quash — any substantive response to the issuing party or court): Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md. If the Role is Non-lawyer:

Responding to a subpoena has legal consequences — missing a deadline risks contempt, over-producing waives privilege, under-producing risks sanctions. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:

[Generate a 1-page summary: the subpoena type, issuing authority, deadlines, scope of what's sought, objections framework and strength, privilege and burden issues, proposed response posture, what could go wrong, what to ask the attorney.]

If you need to find a licensed attorney, solicitor, barrister, or other authorised legal professional in your jurisdiction: your professional regulator's referral service is the fastest starting point (state bar in the US, SRA/Bar Standards Board in England & Wales, Law Society in Scotland/NI/Ireland/Canada/Australia, or your jurisdiction's equivalent).

Do not proceed past this gate without an explicit yes. Triage, scoping, and internal calendaring do not require the gate — the response to the issuing authority does.

  • If classified as grand jury subpoena → stop, flag for escalation per ~/.claude/plugins/config/claude-for-legal/litigation-legal/CLAUDE.md, do not proceed with standard triage.
  • If classified as CID: flag that regulator-specific norms apply; recommend outside regulatory counsel.
  • Otherwise: offer to create a matter (usually yes — subpoenas are almost always material enough to track).
  • If a legal hold isn't issued with subpoena scope, hand off to /legal-hold --issue immediately.

Close with the next-steps decision tree

End with the next-steps decision tree per CLAUDE.md ## Outputs. Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.

What this skill does not do

  • Draft the final objections letter. Produces the framework; the letter is drafted by user + outside counsel (future: a dedicated objections-draft skill).
  • Move to quash. Surfaces the option; the motion is legal work that requires jurisdiction-specific analysis.
  • Validate rules across jurisdictions. The Step 0 research produces the operative rule for this subpoena; the skill doesn't independently confirm currency or local variants. Flag for counsel verification before acting.
  • Handle grand jury subpoenas. Escalates. This is outside the triage scope.

© 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

Files

Just SKILL.md in litigation-legal/skills/subpoena-triage of anthropics/claude-for-legal.

Open the folder on GitHubat commit 4a6c651

Used in 1 other repository

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.

Compare with similar skills

Subpoena Triage 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.

Subpoena Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Subpoena Triage this skillanthropics/claude-for-legal9.6k1 repos~4.5kAutomated safety check: PassApache-2.0
Tw Legal RAGaa0101181514/tw-legal-rag328—~580Automated safety check: PassCustom licence
Design Award SearchSeanJ1ang/design-judge-skills712—~3kAutomated safety check: PassApache-2.0
China Lawyer AnalystCSlawyer1985/china-lawyer-analyst196—~3.3kAutomated safety check: PassNone
Free Willsyahiidkamil/Software-Engineer-AI-Agent-Atlas401—~3.4kAutomated safety check: PassNone
Billing And Litigation BudgetTHUYRan/Legal-Skills-Chinese874—~5kAutomated safety check: PassNone

Similar skills

  • Tw Legal RAG

    aa0101181514/tw-legal-rag

    Retrieve real Taiwan court judgments with verifiable citations before answering any question about Taiwan law or case law.

    328 GitHub stars~580 tokensUpdated 2 days ago
    Legal & ComplianceAuto-check passed

  • Design Award Search

    SeanJ1ang/design-judge-skills

    Find and verify award-winning designs in the same or adjacent functional category through eight explicit relevance dimensions: problem and user, core function, sensing technology, intervention…

    712 GitHub stars~3k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

  • China Lawyer Analyst

    CSlawyer1985/china-lawyer-analyst

    通过中国法律视角分析事件，运用成文法解释、指导案例参照、请求权基础分析等方法， 理解权利义务、评估责任风险、识别法律依据并推荐合规策略。

    196 GitHub stars~3.3k tokensUpdated 8 mo ago
    Legal & ComplianceAuto-check passed

  • Free Will

    syahiidkamil/Software-Engineer-AI-Agent-Atlas

    Deliberate-choice procedure for a medium-to-high-stakes engineering fork — when the first plausible solution (the instinct, the default next-token pull) would be costly to get wrong.

    401 GitHub stars~3.4k tokensUpdated 3 mo ago
    DatabasesAuto-check passed

  • Billing And Litigation Budget

    THUYRan/Legal-Skills-Chinese

    A skill your agent uses when the user needs to track or manage attorney hours, expert fees, and investigation costs; control litigation spend; or prepare timesheets or expense statements for clients.

    874 GitHub stars~5k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed

  • Case Lifecycle Planning

    THUYRan/Legal-Skills-Chinese

    Case full-lifecycle planning skill. An agent skill from THUYRan/Legal-Skills-Chinese.

    874 GitHub stars~1k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

More from anthropics/claude-for-legal

All 147 skills in this repo

  • Legal Clinic Client Intake

    anthropics/claude-for-legal

    Official

    Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.

    9.6k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed

  • Supervisor Review Queue

    anthropics/claude-for-legal

    Official

    Holds student work in a queue for a legal clinic professor to approve, edit-then-approve or return before anything reaches clients or courts.

    9.6k GitHub starsUsed in 3 repos~1.1k tokens
    Auto-check passed

  • Tabular Document Review

    anthropics/claude-for-legal

    Official

    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.

    9.6k GitHub starsUsed in 3 repos~4.3k tokens
    Auto-check passed

  • Product Launch Legal Review

    anthropics/claude-for-legal

    Official

    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.

    9.6k GitHub starsUsed in 2 repos~5k tokens
    Auto-check passed

  • Legal Skills Registry Browser

    anthropics/claude-for-legal

    Official

    Searches watched registries for community legal skills, shows matches with descriptions and offers the full SKILL.md before anything is installed.

    9.6k GitHub starsUsed in 2 repos~620 tokens
    Auto-check passed

  • Contract Renewal Tracker

    anthropics/claude-for-legal

    Official

    Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.

    9.6k GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

Questions about Subpoena Triage

What does Subpoena Triage do?

Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar. Subpoena Triage is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Triage a subpoena served on the company — classify it, analyze scope/burden/privilege, cross-check the portfolio, and produce an objections framework, compliance plan, and deadline calendar.

When should I use Subpoena Triage?

Subpoena Triage fits situations like: the user says we got a subpoena; served with a subpoena; shares a subpoena; third-party document request to evaluate.

How do I install Subpoena Triage in Claude Code?

Run `npx skills add anthropics/claude-for-legal --skill subpoena-triage -a claude-code`. Or copy the skill folder (litigation-legal/skills/subpoena-triage in anthropics/claude-for-legal) into .claude/skills/subpoena-triage in your project. Claude Code loads it when a task matches its description.

How do I install Subpoena Triage in Codex?

Run `npx skills add anthropics/claude-for-legal --skill subpoena-triage -a codex`. Or copy the skill folder (litigation-legal/skills/subpoena-triage in anthropics/claude-for-legal) into .agents/skills/subpoena-triage in your project. Codex loads it when a task matches its description.

Can I use Subpoena Triage in Cursor, Gemini CLI or GitHub Copilot?

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 subpoena-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/subpoena-triage, .gemini/skills/subpoena-triage, .github/skills/subpoena-triage and .opencode/skills/subpoena-triage in your project.

What does Subpoena Triage need to run?

SKILL.md names no scripts, command-line tools or credentials: Subpoena Triage is instructions for the agent only.

Does Subpoena Triage access the network?

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.

Is Subpoena Triage safe to install?

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.

What licence does Subpoena Triage use?

Subpoena Triage 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.

How many tokens does Subpoena Triage use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Subpoena Triage?

Skills that share tags, products or a category with Subpoena Triage: Tw Legal RAG (aa0101181514/tw-legal-rag, 328 stars), Design Award Search (SeanJ1ang/design-judge-skills, 712 stars), China Lawyer Analyst (CSlawyer1985/china-lawyer-analyst, 196 stars) and Free Will (syahiidkamil/Software-Engineer-AI-Agent-Atlas, 401 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Subpoena Triage?

anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,633 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.