BD case-briefer
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.
Produces detailed law-school case briefs of United States judicial opinions in a fixed nine-section structure: memory jogger, facts, procedural history…
As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (case-briefer) differs from the folder (case-briefer-seth-chandler)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 38 steps
- 100Execution cost. Instruction body is 1685 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1015: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 9 example trigger phrases
- +4Structure: 26 headings
- +3Step-by-step instructions: 38 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.