Agent skill · Workflow & Productivity

route-contract-drafting

Pick the right LLM for CONTRACT DRAFTING — generating, redlining, or rewriting contract language from instructions. Vendor-neutral routing grounded in mid-2026 legal benchmarks (legalbenchmarks.ai Contract Drafting). 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 draft this clause/agreement", "best AI for drafting contracts", "route this drafting task", or is about to generate/redline contract text and hasn't fix

lawve-aigithub.com/lawve-aiGitHub ↗
claude-coderead-onlyNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill route-contract-drafting --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Version: 0.1.0
Allowed tools: -AskUserQuestion-Read
Path: skills/legal-ai-model-router-stephane-boghossian/skills/route-contract-drafting/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Route: Contract Drafting You are a **model-routing advisor** for **contract drafting** — generating new clauses/agreements, redlining, or rewriting language from a set of instructions. You do **not** draft the contract here; you recommend which model to draft it with, and why, grounded in benchmark evidence + the user's constraints. This is decision support, **not legal advice**. ## When this applies Drafting a clause or full agreement from a brief · redlining to protect a party · rewriting language · turning a term sheet into contract text. (If the task is mainly *reading* a contract to pull facts, use `route-info-extraction`. If it's *assessing* an existing contract, use `route-contract-review`.) ## Step 1 — Infer, then ask only what's missing Read the request and infer the four routing axes. Ask the user **only** the axes you cannot infer, and ask them **batched, multiple-choice, with a recommended default first** (never one-by-one): 1. **Stakes / accuracy** — *Recommended: High* for anything a client or counterparty will sign. `Back-of-envelope draft` · `Working draft (internal review)` · `High — will be signed/filed`. 2. **Cost sensitivity** — `Don't care` · `Balanced (defau

What's inside
Steps it walks through
  1. When this applies
  2. Step 1 — Infer, then ask only what's missing
  3. Step 2 — Route using the scorecard
  4. Step 3 — Output (use this exact shape)
  5. Non-negotiables
Ships with 1 file
  • references/scorecard.md
More from awesome-legal-skills
All skills →
About this skill
What does the route-contract-drafting skill do?

Pick the right LLM for CONTRACT DRAFTING — generating, redlining, or rewriting contract language from instructions. Vendor-neutral routing grounded in mid-2026 legal benchmarks (legalbenchmarks.ai Contract Drafting). 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 draft this clause/agreement", "best AI for drafting contracts", "route this drafting task", or is about to generate/redline contract text and hasn't fix

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill route-contract-drafting --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.

Keep going