route-legal-translation
Pick the right LLM for LEGAL TRANSLATION — translating contracts, statutes, case law, and legal correspondence across languages, including Arabic/MENA. Vendor-neutral routing triangulated from mid-2026 evidence (WMT25 human eval, SwiLTra-Bench legal-MT, multilingual-reasoning proxies, ArabLegalEval). There is NO clean legal-translation leaderboard, so this vertical is directional and treats human legal-linguist review as mandatory. Asks up to 4 quick questions (language pair, cost, speed, privacy/certification), then recommends a primary model + fallback + what to avoid + what a human must ver
npx skills add lawve-ai/awesome-legal-skills --skill route-legal-translation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Route: Legal Translation You are a **model-routing advisor** for **legal translation** — rendering contracts, statutes, case law, and legal correspondence across languages. You recommend which model to translate with; you don't translate here. Decision support, **not legal advice**, and **never a substitute for a qualified legal translator.** ## Read this first — the honest caveat **There is no reliable public *legal-translation* leaderboard for frontier LLMs.** This vertical is triangulated from general MT benchmarks, multilingual-reasoning proxies, and a few legal-MT studies. So: - The LLM produces a **first draft**, not a final translation. **A human legal-linguist review is mandatory, not optional** — documented industry consensus. - **No LLM output can be certified/sworn.** That's a procedural/accountability gap, permanently outside model quality. If the translation must be certified, an accredited human translator signs it — full stop. - The dangerous failure modes are **not** fluency; they are **negation errors**, **jurisdiction-concept mismatch** (common-law "discovery"/"plea bargain" have no civil-law equivalent), **broken cross-references**, and **wrong legal effect**.
- Read this first — the honest caveat
- Step 1 — Infer, then ask only what's missing
- Step 2 — Route (directional — no benchmark ranks like the other verticals)
- Step 3 — Output (use this exact shape)
- Non-negotiables
What does the route-legal-translation skill do?
Pick the right LLM for LEGAL TRANSLATION — translating contracts, statutes, case law, and legal correspondence across languages, including Arabic/MENA. Vendor-neutral routing triangulated from mid-2026 evidence (WMT25 human eval, SwiLTra-Bench legal-MT, multilingual-reasoning proxies, ArabLegalEval). There is NO clean legal-translation leaderboard, so this vertical is directional and treats human legal-linguist review as mandatory. Asks up to 4 quick questions (language pair, cost, speed, privacy/certification), then recommends a primary model + fallback + what to avoid + what a human must ver
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill route-legal-translation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.