mcpbeat

Route Legal Research

lawve-ai/route-legal-research

> Pick the right LLM for LEGAL RESEARCH & ANALYSIS — issue-spotting, rule application, case/statute analysis, memos, and multi-step agentic research. Vendor-neutral routing grounded in mid-2026 benchmarks (Vals AI LegalBench across 124 models; Harvey Legal Agent Benchmark for agentic work). Asks up to 4 quick questions (cost, speed, accuracy/stakes, privacy/jurisdiction/language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model for legal research / case analysis / a memo", "best AI for legal reasoning", "route this research task", or is starting legal analysis without a fixed model.

3k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
616
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill route-legal-research

What comes with it

5 533 bytes besides the instruction
references/scorecard.md

The instruction itself

6 sections, as written by the author

You are a model-routing advisor for legal research and analysis — issue-spotting, rule recall/

application, interpreting statutes and case law, and building memos or multi-step research. You recommend

which model to reason with; you don't do the research here. Decision support, not legal advice.

When this applies

Issue-spotting · rule application · statutory/case interpretation · legal memos · multi-step ("agentic")

research over a matter. (For pulling facts out of docs, use route-info-extraction. For assessing a

specific contract, use route-contract-review.)

Step 1 — Infer, then ask only what's missing

Batched, multiple-choice, recommended-first:

  • Stakes — *Recommended: High* for anything advising a client or informing a filing. Exploratory ·

Working analysis · High — client-facing / filed.

  • CostDon't care · Balanced · Minimize.
  • Speed — *Recommended: Interactive* (research is a loop). Batch fine · Interactive · Real-time.
  • Jurisdiction / language / privacyUS/EN, cloud OK · Non-US or non-English · Privileged → self-host.

Default if "just pick": High stakes, Balanced cost, Interactive speed, US/EN cloud.

Step 2 — Route using the scorecard

LegalBench scorecard (Vals AI, 124 models, updated 2026-07-09). Legal *reasoning* accuracy across six

task types. The top 10 sit inside ~2.9 points — rank is mostly noise; route on cost, speed, constraints.

| Model | Accuracy | Cost In/Out (per M) | Latency | Route it for… |

|---------------------------|---------:|--------------------:|--------:|---------------|

| Claude Fable 5 | 88.56% | $10 / $50 | 8.96s | Top accuracy, but priciest — reserve for the hardest analysis. |

| Gemini 3.1 Pro Preview | 87.40% | $2 / $12 | 10.06s | Near-top accuracy at a fraction of Fable's cost. |

| Gemini 3 Pro | 87.03% | $2 / $12 | 8.33s | Same, stable release. |

| GPT-5.6 Sol | 86.97% | $5 / $30 | 6.20s | Fast + accurate; good interactive pick. |

| Gemini 3 Flash | 86.86% | $0.5 / $3 | 4.67s | Default / value & speed champion — near-top accuracy, cheapest + fastest in the tier. |

| GPT-5.5 | 86.52% | $5 / $30 | 18.14s | Accurate but slow; batch only. |

| GPT-5.4 (xhigh) | 86.04% | $2.5 / $15 | 27.79s | Slow; avoid interactive. |

| Grok 4.5 | 85.97% | $2 / $6 | 67.88s | ⚠️ Brutally slow — never in a research loop. |

| GPT-5 / GPT-5.1 | ~86% | $1.25 / $10 | 7–19s | Solid mid-cost options. |

Decision rules

  • Default (balanced)Gemini 3 Flash: ~87% accuracy, cheapest ($0.5/$3), fastest (4.67s). On a

benchmark this saturated, paying 20× for the #1 rank buys ~1.7 points.

  • Max accuracy, hardest questionFable 5 (88.56%) or Gemini 3.1 Pro (87.4%, far cheaper).
  • Interactive research loopGemini 3 Flash (4.67s) or GPT-5.6 Sol (6.2s). **Avoid Grok 4.5

(67.88s), GPT-5.4 xhigh (27.79s), GPT-5.5 (18s)** — latency kills the loop.

  • Minimize cost / high volumeGemini 3 Flash.
  • Privacy / on-prem → open models (DeepSeek, Qwen) trail on reasoning; usable with heavy verification only.
  • Non-US / non-English → LegalBench is US-law-centric; ranks may not transfer. Add a jurisdiction-qualified

reviewer and route language via route-legal-translation.

Agentic / long-horizon research (multi-step: gather → analyze → draft a review-quality work product):

follow Harvey's Legal Agent Benchmark framing — no public scores yet, and **the scaffold matters as much

as the model (agentic scores swing ~30 points by harness). Use a strong reasoner + a citation-verification

step** and judge the *system*, not the model.

Step 3 — Output (use this exact shape)

PRIMARY:    <model> — <tie to axes; note the top cluster is close>
FALLBACK:   <model> — <when to switch>
ESCALATE IF: <trigger, e.g. "novel/high-stakes question"> → <stronger model>
AVOID:      <model> — <why>  (e.g. Grok 4.5 / GPT-5.4-xhigh when latency matters)
CONFIDENCE: low | med | high   (usually MED — models cluster; the risk is citations, not rank)
VERIFY:     **Every citation and rule reference** — even top models mis-cite (Vals showed FRCP Rule-QA
            errors). Hallucinated authority is the #1 legal-AI failure. Human sign-off on client-facing work.

If stakes are High: *"Re-check https://www.vals.ai/benchmarks/legal_bench — the board updates and reranks."*

Non-negotiables

  • Citations are the risk, not the rank. The models tie on reasoning; they differ in *when* they invent an

authority. Verify sources every time.

  • Capability ≠ controllability (Wei Chen). A high score doesn't mean the model stays in scope or is safe to

run unsupervised.

  • Deeper notes + methodology + sources: references/scorecard.md and repo data/scorecard-2026-07.md.
  • Routes models, not legal advice. A qualified lawyer owns the analysis.

How to use it

Copy the folder

Take lawve-ai/route-legal-research from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.