Agent skill

Route Info Extraction

by lawve-ai in lawve-ai/awesome-legal-skills

Pick the right LLM for LEGAL INFO EXTRACTION — pulling facts, clauses, dates, parties, obligations, and structured fields out of contracts and legal documents.

AGPL-3.0-or-laterAuto-check passedLegal & Compliance

Install Route Info Extraction

skills CLI
$ npx skills add lawve-ai/awesome-legal-skills --skill route-info-extraction -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install lawve-ai/awesome-legal-skills route-info-extraction --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/legal-ai-model-router-stephane-boghossian/skills/route-info-extraction .claude/skills/route-info-extraction && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
route-info-extraction
GitHub stars
847
Token cost
~1.5k tokens
SKILL.md length
556 words
Files
2 (incl. references)
Skills in repo
154
Repo updated
First seen
Licence
AGPL-3.0-or-later

At a glance

Pick the right LLM for LEGAL INFO EXTRACTION — pulling facts, clauses, dates, parties, obligations, and structured fields out of contracts and legal documents.

  • Works in 3 steps: Infer, then ask only what's missing → Route using the scorecard → Output (use this exact shape)
  • Someone asks which model should I use to extract clauses/data from these documents
  • SKILL.md covers When this applies, Step 1 — Infer, then ask only…, Step 2 — Route using the… and Step 3 — Output (use this…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Route Info Extraction is an agent skill from lawve-ai/awesome-legal-skills. Pick the right LLM for LEGAL INFO EXTRACTION — pulling facts, clauses, dates, parties, obligations, and structured fields out of contracts and legal documents. Vendor-neutral routing grounded in mid-2026 benchmarks (legalbenchmarks.ai Info Extraction; CUAD/MAUD/ACORD). 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 should I use to extract…

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/scorecard.md`).

It sits in Legal & Compliance, covering Policy and terms drafting and Contract review. The repository describes itself as: A curated list of awesome Agent Skills for automating legal work. The licence is AGPL-3.0-or-later.

When your agent uses it

  • Someone asks which model should I use to extract clauses/data from these documents
  • Best AI for contract data extraction
  • Route this extraction task
  • Is about to pull structured fields from legal docs without a fixed model

Example prompts

  • “which model should I use to extract clauses/data from these documents”
  • “best AI for contract data extraction”
  • “route this extraction task”
  • “/route-info-extraction”

Requirements

  • Pre-approved tools (allowed-tools): AskUserQuestion, Read

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Infer, then ask only what's missing
  2. Route using the scorecard
  3. Output (use this exact shape)

What it can do on your machine

Read from SKILL.md and the folder at commit 045f738. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • AskUserQuestion
    • Read

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • legalbenchmarks.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Route Info Extraction loads about 1.5k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 178 tokens; SKILL.md has 556 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~178
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from lawve-ai/awesome-legal-skills at commit 045f738, republished under its AGPL-3.0-or-later licence (© lawve-ai). 556 words, ~1,507 tokens.

Download SKILL.mdSave it as .claude/skills/route-info-extraction/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
route-info-extraction
description
Pick the right LLM for LEGAL INFO EXTRACTION — pulling facts, clauses, dates, parties, obligations, and structured fields out of contracts and legal documents. Vendor-neutral routing grounded in mid-2026 benchmarks (legalbenchmarks.ai Info Extraction; CUAD/MAUD/ACORD). 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 should I use to extract clauses/data from these documents", "best AI for contract data extraction", "route this extraction task", or is about to pull structured fields from legal docs without a fixed model.
allowed-tools
AskUserQuestion, Read
version
0.1.0
triggers
which model should I use to extract clauses or data from these documents, best AI for contract data extraction, route this extraction task, pull structured…
license
AGPL-3.0-or-later

Route: Info Extraction

You are a model-routing advisor for legal information extraction — pulling clauses, parties, dates, amounts, obligations, and structured fields out of contracts and legal documents. You recommend which model to extract with, and why; you do not do the extraction here. Decision support, not legal advice.

When this applies

Clause extraction · obligations/dates/parties tables · cross-document field comparison · due-diligence data capture · turning a stack of PDFs into structured data. (If you're generating text, use route-contract- drafting. If you're assessing the contract's risk, use route-contract-review.)

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

Ask batched, multiple-choice, recommended-default-first, only for axes you can't infer:

  1. Stakes — Recommended: High if the extracted data drives a decision or filing. Triage/exploratory · Working · High — decisions rely on it.
  2. Cost — Don't care · Balanced · Minimize $/task (extraction is often high-volume → cost matters).
  3. Speed — Batch fine · Interactive · Real-time.
  4. Document type & privacy — ask this one almost always, it changes the pick: Clean digital text · Scanned / image PDFs · Non-English · Client-privileged → self-hostable.

Default if "just pick": High stakes, Balanced cost, Batch speed, Clean digital English docs.

Step 2 — Route using the scorecard

Info Extraction scorecard (legalbenchmarks.ai, 29 tasks, data as of 2026-07). Documents are sent native/unconverted, so file-reading (incl. scans) is part of the test. Reliability = all-pass on a lawyer checklist.

ModelReliabilityCost/taskRoute it for…
GPT 5.6 Sol89.7%~$0.19Default (clean digital docs). Best exhaustive clause retrieval + cross-doc comparison.
Claude Opus 4.886.2%~$0.29Safest read. Most dependable; route here when you'll trust the output without re-checking every field.
Claude Fable 586.2%~$0.63Ties Opus; pick Opus unless already in a Fable pipeline (costs more).
GPT-5.582.8%$0.15Cheaper GPT option, small reliability drop.
Grok 4.579.3%~$0.19Scanned / image PDFs — best OCR-adjacent handling of any model. Then check completeness.
Claude Sonnet 4.672.4%$0.13Balanced mid-tier for working extraction.
Gemini 3.1 Pro / 3.5 Flash65.5%$0.07–0.08Cheapest/fastest for lower-stakes or high-volume triage.
DeepSeek V4 Pro / GPT-5.4-mini / Qwen 3.7 Max55–62%$0.01–0.03Cheap triage only; heavy human review.

Decision rules

Show full SKILL.md (221 more words)Show less
  • Default / max accuracy on clean digital docs → GPT 5.6 Sol (89.7%). Guardrail: it flattens conditional answers into absolutes ("if X, then Y" → "Y"). Always verify any conditional/qualified field.
  • You want the dependable read you won't re-check → Opus 4.8 (86.2%): fewer surprises, but the most verbose output (budget output tokens + post-processing).
  • Scanned / image / handwriting-adjacent PDFs → Grok 4.5 — best scanned handling, but it under-returns on completeness ("almost all"). Route here for OCR-heavy sets, then run a coverage check.
  • High volume / low stakes / speed → Gemini 3.5 Flash (~$0.08, fast). Accept ~65% reliability for triage.
  • Privacy / on-prem → Qwen 3.7 Max or DeepSeek V4 Pro (55–62%) — usable only with heavy review; state the reliability cost.
  • Non-English → hand off language handling to route-legal-translation; extraction ranks here are English-only.

Reproducible extraction datasets (for building your own eval): CUAD (clause extraction, 41 types), MAUD (M&A reading comprehension), ACORD (clause retrieval) — the Atticus Project open sets.

Step 3 — Output (use this exact shape)

PRIMARY:    <model> — <tie to axes + doc type>
FALLBACK:   <model> — <when to switch>
ESCALATE IF: <trigger, e.g. "conditional-heavy fields / decision rides on it"> → <stronger model>
AVOID:      <model> — <why, for THIS task>  (e.g. cheap tier when accuracy matters; GPT 5.6 Sol on scans)
CONFIDENCE: low | med | high
VERIFY:     Conditional fields not flattened · coverage is complete (all-pass) · scanned pages actually read.

If stakes are High: "Re-check https://www.legalbenchmarks.ai/leaderboard — extraction ranks shift monthly."

Non-negotiables

  • Completeness is binary here: an obligations table that misses one obligation is not 95% done, it's wrong.
  • Capability ≠ controllability — a top score doesn't mean the model won't confidently invent a field.
  • Deeper per-model notes + methodology + sources: references/scorecard.md and repo data/scorecard-2026-07.md.
  • Routes models, not legal advice. A qualified lawyer owns any decision built on the extracted data.

© lawve-ai, AGPL-3.0-or-later. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/legal-ai-model-router-stephane-boghossian/skills/route-info-extraction of lawve-ai/awesome-legal-skills.

  • SKILL.md
  • references/scorecard.md

Open the folder on GitHubat commit 045f738

Compare with similar skills

Route Info Extraction next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Route Info Extraction compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Route Info Extraction this skilllawve-ai/awesome-legal-skills847—~1.5kAutomated safety check: PassAGPL-3.0-or-later
Pii Contract Analyzegregmos/PII-Shield150—~8.9kAutomated safety check: NotesMIT
Contract Drafterrohasnagpal/legal-ai-skills180—~3.6kAutomated safety check: PassMIT
Contract ReviewTheCraigHewitt/skills159—~1.6kAutomated safety check: PassMIT
Legal Concept ComprehensionTHUYRan/Legal-Skills-Chinese874—~7.9kAutomated safety check: PassNone
Legal Contract Genrongxinzy/RongxinAI154—~3.2kAutomated safety check: PassMIT

Similar skills

  • Pii Contract Analyze

    gregmos/PII-Shield

    Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.

    150 GitHub stars~8.9k tokensUpdated 3 mo ago
    Legal & ComplianceAuto-check: notes
  • Contract Drafter

    rohasnagpal/legal-ai-skills

    Drafts a complete contract from a term sheet, negotiated heads or plain instructions — parties, recitals, definitions, operative clauses, schedules and boilerplate — in a specified posture and…

    180 GitHub stars~3.6k tokensUpdated today
    Legal & ComplianceAuto-check passed
  • Contract Review

    TheCraigHewitt/skills

    Review a contract, agreement, terms-of-service, MSA, NDA, employment agreement, vendor SOW, or any legal document.

    159 GitHub stars~1.6k tokensUpdated 4 mo ago
    Legal & ComplianceAuto-check passed
  • Legal Concept Comprehension

    THUYRan/Legal-Skills-Chinese

    Trigger this skill when the user asks to explain, distinguish, unpack, or understand a legal concept.

    874 GitHub stars~7.9k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Legal Contract Gen

    rongxinzy/RongxinAI

    通过交互式问答生成常用法律文书初稿,支持NDA(保密协议)、服务协议、隐私政策、合作框架协议等类型。当用户提到NDA、保密协议、服务协议、隐私政策、合同模板、法律文书、合作协议,或相应的英文术语(如terms of service、privacy policy、service agreement、non-disclosure agreement、contract template、legal…

    154 GitHub stars~3.2k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed
  • Contract Standards Ingest

    infometa/workbuddyskills

    Ingest and standardize user-provided contract assets — existing template libraries, sample contracts, clause banks, rule/standard libraries, review playbooks, checklists, past review opinions…

    348 GitHub stars~1.4k tokensUpdated yesterday
    Legal & ComplianceAuto-check passed

More from lawve-ai/awesome-legal-skills

All 154 skills in this repo
  • Customs Trade Law Onur Kafkas

    lawve-ai/awesome-legal-skills

    U.S. An agent skill from lawve-ai/awesome-legal-skills.

    847 GitHub stars~4.1k tokensUpdated 8 days ago
    Auto-check passed
  • Eu Data Act Oliver Schmidt Prietz

    lawve-ai/awesome-legal-skills

    Practitioner skill for advising on EU Regulation 2023/2854 (Data Act).

    847 GitHub stars~3.9k tokensUpdated 8 days ago
    Auto-check passed
  • Litigation Deadline Calendar

    lawve-ai/awesome-legal-skills

    Calendar litigation and arbitration deadlines from a scheduling order.

    847 GitHub stars~4.3k tokensUpdated 8 days ago
    Auto-check passed
  • Outlook Emails Lawvable

    lawve-ai/awesome-legal-skills

    Read, search, and download emails and attachments from Microsoft Outlook via OAuth2.

    847 GitHub stars~672 tokensUpdated 8 days ago
    Auto-check passed
  • Ambiguity Report

    lawve-ai/awesome-legal-skills

    Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable.

    847 GitHub stars~4.6k tokensUpdated 8 days ago
    Auto-check passed
  • Az Eu Website Privacy Audit

    lawve-ai/awesome-legal-skills

    Audits a website for compliance with Azerbaijan's Law on Personal Data No.

    847 GitHub stars~3.8k tokensUpdated 8 days ago
    Auto-check passed

Questions about Route Info Extraction

What does Route Info Extraction do?

Pick the right LLM for LEGAL INFO EXTRACTION — pulling facts, clauses, dates, parties, obligations, and structured fields out of contracts and legal documents. Route Info Extraction is an agent skill from lawve-ai/awesome-legal-skills. Pick the right LLM for LEGAL INFO EXTRACTION — pulling facts, clauses, dates, parties, obligations, and structured fields out of contracts and legal documents.

When should I use Route Info Extraction?

Route Info Extraction fits situations like: someone asks which model should I use to extract clauses/data from these documents; best AI for contract data extraction; route this extraction task; is about to pull structured fields from legal docs without a fixed model.

How do I install Route Info Extraction in Claude Code?

Run `npx skills add lawve-ai/awesome-legal-skills --skill route-info-extraction -a claude-code`. Or copy the skill folder (skills/legal-ai-model-router-stephane-boghossian/skills/route-info-extraction in lawve-ai/awesome-legal-skills) into .claude/skills/route-info-extraction in your project. Claude Code loads it when a task matches its description.

How do I install Route Info Extraction in Codex?

Run `npx skills add lawve-ai/awesome-legal-skills --skill route-info-extraction -a codex`. Or copy the skill folder (skills/legal-ai-model-router-stephane-boghossian/skills/route-info-extraction in lawve-ai/awesome-legal-skills) into .agents/skills/route-info-extraction in your project. Codex loads it when a task matches its description.

Can I use Route Info Extraction in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lawve-ai/awesome-legal-skills --skill route-info-extraction -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/route-info-extraction, .gemini/skills/route-info-extraction, .github/skills/route-info-extraction and .opencode/skills/route-info-extraction in your project.

What does Route Info Extraction need to run?

SKILL.md names no scripts, command-line tools or credentials: Route Info Extraction is instructions for the agent only. Its frontmatter pre-approves these tools: AskUserQuestion, Read.

Does Route Info Extraction access the network?

SKILL.md names 1 domain. As links in the text: legalbenchmarks.ai. This is read from the text; nothing was executed.

Is Route Info Extraction safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Route Info Extraction use?

Route Info Extraction is published under the AGPL-3.0-or-later licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Route Info Extraction use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Route Info Extraction?

Skills that share tags, products or a category with Route Info Extraction: Pii Contract Analyze (gregmos/PII-Shield, 150 stars), Contract Drafter (rohasnagpal/legal-ai-skills, 180 stars), Contract Review (TheCraigHewitt/skills, 159 stars) and Legal Concept Comprehension (THUYRan/Legal-Skills-Chinese, 874 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Route Info Extraction?

lawve-ai (a GitHub organization) maintains it in lawve-ai/awesome-legal-skills, which has 847 GitHub stars. The repository holds 154 skills in this directory. The repository was last updated on October 2, 2026.

Source: lawve-ai/awesome-legal-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.