skills/case-briefer-seth-chandler/SKILL.md
Produces detailed law-school case briefs of United States judicial opinions in a fixed nine-section structure: memory jogger, facts, procedural history, judicial votes, holding, opinion-by-opinion analysis, five future-application hypotheticals, critique, and verified key quotations. Also builds vote tables, cross-case consistency tables, perspective-based critiques, and LaTeX in article, Beamer and casebook-chapter formats. Use whenever someone asks to brief a case, analyse or explain an opinion, summarise a decision for students, generate hypotheticals from a holding, critique a judgment, tabulate how justices voted, or convert case analysis to LaTeX. Triggers on "brief this case", "case brief", "explain the holding", "what did the court hold", "hypotheticals based on", "critique this opinion", "vote table", "Beamer presentation", "chapter brief", and on any reference to a judicial opinion or Supreme Court decision in a teaching context. Requires web search to verify quotations, votes and holdings.
npx skillsauth add lawvable/awesome-legal-skills case-brieferInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Deliver detailed case briefs with comprehensive analysis, examples, and critique for law students and professors.
Every case brief includes these 9 sections:
One sentence capturing the case's essence — its facts, central holding, or most salient feature.
Include:
Focus on procedural aspects relevant to disposition:
Group by:
Succinct statement of the court's judgment and the rule announced.
For each opinion (majority, concurrences, dissents):
Create 5 hypotheticals showing how the rule applies:
For each, explain why it falls where it does under the rule.
Present 3–5 important quotes from the opinions, subject to the verification rule below.
Quotations, vote counts, and holdings are the three places this skill can do real damage if it is wrong, because each is the kind of claim a reader will repeat without checking.
Distinguish holdings from dicta. Note circuit splits, later overruling, and subsequent statutory or doctrinal developments where relevant.
Engage in dialogue about cases as in normal conversation.
When asked for specific quotations, apply the verification rule above.
Create tables showing how each justice or judge voted in a case.
Compare voting patterns across multiple cases — showing which justices voted which way in each case.
Offer critiques from specified perspectives:
Three output formats are supported. The preambles, slide-structure examples, and chapter
skeleton live in resources/latex-preambles.md — read that file when producing LaTeX rather
than reconstructing the preambles from memory.
A standalone brief. Use the article preamble from the resource file.
A slide deck. Use the Beamer preamble from the resource file, and observe the slide limits: roughly 5 main items per slide, at most 2 subitems each, and no more than 9 items and subitems in total.
Input pattern: Brief [Case Name]. Emphasize [Specific Concept or Historical Context]
Output: a modular LaTeX chapter file for \input{filename} in a larger book project.
Do NOT include a document class, package imports, or any preamble — the parent document
supplies them. Begin at \chapter{} and follow the section skeleton in the resource file,
which mirrors the nine-section structure above.
resources/latex-preambles.md — article and Beamer preambles, Beamer slide guidelines and
a worked slide example, and the no-preamble chapter skeleton. Read when producing any
LaTeX output.This skill produces teaching and study materials about United States judicial opinions. It is not legal advice and does not produce authority. A brief generated here is a study aid: it must not be cited, filed, or relied upon in practice in place of reading the opinion.
Three risks are worth naming. First, quotation and vote-count accuracy depends on web search being available and on the opinion text being reachable; without it the model may reconstruct plausible but incorrect language, which is why the verification rule requires unverified material to be marked or omitted. Second, briefs reflect the state of the law at the time of generation and will not know of later overruling, vacatur, or amendment unless the search surfaces it. Third, the critique and perspective sections are argumentative by design — they present the strongest form of a position, including positions the user did not ask about, and should not be read as a neutral account of scholarly consensus.
The skill contains no executable code, makes no network calls of its own beyond the host's web search, and moves no data outside the session.
development
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
development
Expert CMMC 2.0 (Cybersecurity Maturity Model Certification) advisor for US defense contractors and subcontractors in the Defense Industrial Base (DIB). Use this skill whenever a user asks about CMMC 2.0, CMMC Level 1, Level 2, or Level 3, DoD cybersecurity compliance, NIST SP 800-171, CUI (Controlled Unclassified Information) protection, System Security Plan (SSP), Plan of Action & Milestones (POA&M), C3PAO assessments, DIBCAC audits, self-assessment, SPRS score, or any requirement under DFARS 252.204-7012 or 7021. Also trigger for: "CMMC gap analysis", "CMMC readiness", "FCI protection", "CUI scoping", "CMMC practices", "DoD contract cybersecurity", "defense supply chain security", or "prime contractor flow-down requirements".
tools
Build a client instruction schedule — a plain-English, Scott Schedule-style Word table that gathers a struggling client's evidence and instructions issue by issue, with a one-page covering note. Use whenever the user asks for a "client instruction schedule", "instruction schedule", "client questionnaire", "schedule of questions for the client", "get instructions from the client on the papers", or says the client is overwhelmed and needs the case broken into manageable questions. Also trigger when asked to turn case papers into a structured request for client input. Do NOT use for court-facing Scott Schedules, pleadings, witness statements, or advice letters — this skill produces a client-facing working document only. Output is always a .docx draft for solicitor review, never a final document.
tools
Turn complex legal analysis into clear, commercially useful client-facing advice. Use this whenever the user has dense legal material — drafting, internal analysis, counsel notes, research memos, pleadings, a case update, or correspondence — and wants it converted into something a client can actually understand and act on. Trigger on phrases like 'explain this to the client', 'put this in plain English', 'translate this for a non-lawyer', 'turn this into client-facing advice', 'make this client-ready', 'draft a client update', or when the user shares legal analysis and asks 'what does this mean for them'. Also trigger when the user wants a board summary, litigation risk update, or call script derived from legal material. The skill preserves legal nuance, uncertainty, and risk rather than oversimplifying — it makes advice usable, not just simpler.