case-brief
Brief a case in your preferred format. In drill-me mode, makes the student state the holding first. Use when the user says "brief [case]", "what's the holding in", "case brief", or pastes a case.
- Installs
- 638
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/anthropics/claude-for-legal --skill case-brief- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads case-brief automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
/case-brief
- Load
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md→ outline/brief preferences. - Apply the workflow below.
- Brief in the student's format. If drill-me mode: ask the student to state the holding first.
Purpose
A case brief is a tool for remembering what a case does. This skill makes one in your format — the format you'll actually use in your outline.
Confidence discipline
Case briefs state holdings, rules, and reasoning. Getting them wrong turns your outline into a false map. The rule for this skill:
- If you paste the case text: I extract holding/rule/reasoning from what's in front of me. Confident.
- If you only give a case name: I brief from knowledge. Worth a lot less. I flag every line I'm not sure about with
[UNCERTAIN: specific reason], and I strongly recommend you confirm against the actual case before putting the brief in your outline. If I don't know the case well enough, I say so. - If the case has famous-but-contested interpretations: I give the majority read and
[VERIFY: check your casebook and professor's framing].
A brief built on my guess and your good faith is worse than no brief. Better to err toward "I'm not sure — read it yourself" than to invent.
Load context
~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md → outline/brief preferences (format, depth), learning style.
The "don't brief it for me" rule (hard rule)
A brief you didn't write is a brief you won't remember. Every mode of this skill defaults to scaffolding the student's brief-writing, not to writing the brief.
What this skill will do in every mode:
- Ask the student what they already got from reading: the facts, the issue, the holding as they understand it.
- Provide the blank template in their preferred format (headings for Facts, Issue, Holding, Reasoning, Rule, Notes).
- Ask pointed follow-ups on whichever section is thin: "What were the key facts the court actually relied on?", "What's the narrow issue vs. the broader question?", "Why did the court reject the dissent's framing?"
- If the student pastes the case text, extract verbatim the court's own language for holding and reasoning — that is not writing-for-them; that is pointing at what the case says.
- Flag confused or wrong understandings: "You said the holding is X. The court's actual language is closer to Y. Which one is the rule you'll carry into your outline?"
What this skill will not do, even if asked:
- Write a full case brief from a case name alone. That is the exact thing the student is learning not to need.
- "Summarize this case for me" — refused. The brief is for remembering, which requires writing.
Exception (the only one): the student explicitly overrides — "I've read it three times, I'm stuck on phrasing the holding, just give me a starter sentence so I can rewrite it." Then write a minimal starter with [VERIFY] flags and prompt them to rewrite in their own words before it goes into an outline.
Mode fork
Drill-me mode: Ask the student to state the holding before anything else:
"You've read this case. What's the holding? One sentence."
If they can't state it, make them read it again. The brief is a memory aid, not a substitute for reading. Then proceed to the scaffold — ask them to state facts, issue, reasoning, and rule in turn. Push back on thin or wrong statements.
Explain-to-me mode: Same scaffolded workflow, softer tone. The skill walks the student through each section, offers structural prompts ("a good holding is one sentence, yes/no + the rule"), but still waits for the student to write the content. Explain-to-me does not mean "write the brief for me." It means "explain what a good brief looks like, and guide me through writing mine."
If the student pastes the case text in either mode, the skill can extract the court's own language into the Facts/Holding/Reasoning slots — that's not writing-for-them, that's pointing at the source.
The brief — scaffold, then the student fills
The skill produces the template with questions, not the filled-in brief. Student fills each section; skill reviews, pushes back, suggests what's missing.
Per the student's format in ~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md. If none captured, default:
## [Case Name], [cite]
**Court:** [court, year]
**Facts:** [The facts that matter to the holding. Not every fact — the ones
the court relied on. Two to four sentences.]
**Procedural posture:** [How did this get here? Trial court ruled X, this
is an appeal from that. One sentence.]
**Issue:** [The question the court answered. Phrased as a yes/no question.]
**Holding:** [The answer. One sentence. Yes/no + the rule.]
**Reasoning:** [Why. The court's logic. This is where the law is. Three to
five sentences.]
**Rule:** [The rule you'd put in your outline. The portable takeaway.]
**Notes:** [Dissent worth knowing? Distinguishable on these facts? How
professor emphasized it?]
---
**Citation check.** The case cite, quoted language, and any supporting authority above were generated by an AI model and have not been verified. Before you rely on them — in a brief, memo, outline entry, or exam answer — look them up on Westlaw, CourtListener, or your school's research tool. AI-generated citations are sometimes fabricated or misquoted.
Depth calibration
Per ~/.claude/plugins/config/claude-for-legal/law-student/CLAUDE.md — some students want one-line briefs (rule + cite), some want full treatment. Match their format.
If they're a 1L still learning to read cases: fuller briefs. If they're a 3L doing bar prep: rules only.
What this skill does not do
- Brief a case the student hasn't read. In drill-me mode, the holding check enforces this.
- Tell you what's on the exam. Brief everything; the exam will surprise you.
- Brief from memory without flagging. If you only give me a case name and I brief from what I think I know, every line I'm unsure about gets
[UNCERTAIN]or[VERIFY]. Don't put a brief in your outline unless you've confirmed it against the actual case.
FAQ
What does the case-brief skill do?
Brief a case in your preferred format. In drill-me mode, makes the student state the holding first. Use when the user says "brief [case]", "what's the holding in", "case brief", or pastes a case.
How do I install case-brief?
Run npx skills add https://github.com/anthropics/claude-for-legal --skill case-brief in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/case-brief/ (personal) or .claude/skills/case-brief/ (project).
Which AI agents can use case-brief?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is case-brief safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains case-brief?
It is published by anthropics in anthropics/claude-for-legal, and it is an official skill from the maker of the technology it covers. It has 638 recorded installs.
More from anthropics/claude-for-legal
legal-writing
anthropics/claude-for-legal
Structural feedback on a legal writing draft (memo, brief, paper, exam essay) — organization, analysis depth, clarity, citation form. NEVER rewrites the draft. Use when the user says "feedback on my memo", "read my draft", or "critique my brief".
draft
anthropics/claude-for-legal
First draft of a common clinic document — practice-area templates (asylum applications, eviction answers, protective order petitions, demand letters), jurisdiction-aware formatting, explicitly a starting point requiring student analysis and attorney review. Use when a student needs a first draft of a motion, letter, petition, declaration, or other clinic document.
flashcards
anthropics/claude-for-legal
Generate or drill flashcards for black-letter memorization — Leitner-style buckets, per-subject markdown storage, drill mode with self-assessment. Use when the user says "drill flashcards", "make flashcards from", "quiz me on cards", or wants to memorize rules.
saas-msa-review
anthropics/claude-for-legal
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
review
anthropics/claude-for-legal
Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.
policy-monitor
anthropics/claude-for-legal
Keep the privacy policy current with practice. Two modes: weekly sweep of saved PIAs, DPA reviews, and triage results to find policy drift; or direct query for a proposed new practice. Use when the user asks "does our policy cover this", "we want to start doing X — does the policy need updating", "run the policy monitor", "policy sweep", or wants to find where the privacy policy no longer matches what the team actually does.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.