Legal Mdl Audit Ignacio Adrian Lerer Agent Skill
Audits legal AI outputs and workflows for honest compression: unnecessary complexity, false simplicity, excessive caveats, hidden uncertainty and poor cost per legally acceptable output.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/lawve-ai/awesome-legal-skills --skill legal-mdl-audit-ignacio-adrian-lererWhat comes with it
186 bytes besides the instructionThe instruction itself
6 sections, as written by the authorLegal MDL Audit
What this skill does
This skill reviews whether a legal AI answer, prompt, workflow, benchmark result, contract review, memo, compliance report, or agent chain is as simple as it can safely be.
It is inspired by Minimum Description Length: good legal reasoning should explain more with less structure, but never by hiding material uncertainty.
Audit categories
Classify the material as:
- APPROVE: lean and still legally safe.
- APPROVE WITH CONSTRAINTS: complexity is justified, but reliance needs stated limits.
- REWRITE: the output is too complex, repetitive, expensive, or hard to audit.
- QUARANTINE: the output is falsely simple and hides material uncertainty.
Checklist
Review:
- Rules: how many legal propositions are needed?
- Exceptions: how many carve-outs or qualifications are doing real work?
- Conditions: what facts, dates, forums, sources or procedural states must hold?
- Sources: are citations enough, excessive, or missing?
- Uncertainty: what must remain visible?
- Workflow cost: how many model/tool/human steps were needed?
- Output value: did added complexity improve legal acceptability?
Output format
Return:
- Verdict.
- Complexity drivers.
- Hidden uncertainty or omitted hard cases.
- What can be simplified.
- What must not be removed.
- Safer shorter version, if requested.
Rules
- Do not reward short answers that erase legal uncertainty.
- Do not reward long answers that add caveats without improving reliance.
- Prefer cost per legally acceptable output over cost per token or API call.
- Preserve source gaps, authority boundaries and human-review gates.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take lawve-ai/legal-mdl-audit-ignacio-adrian-lerer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.