legal-design-assessment
Audits a legal document against legal design principles. Scores the document on six pillars: language patterns (bureaucratese, archaisms, passive voice, nominalization), readability (Flesch Reading Ease and language-specific equivalents), structure and navigation, hidden conditions (material obligations buried away from their headings), statutory duplication (restating the law instead of citing it), and visual hierarchy where layout is available. Assessment-only; does not rewrite the document. Works on English, French, and German documents, inferring the applicable jurisdiction from the docume
npx skills add lawve-ai/awesome-legal-skills --skill legal-design-assessment-mirza-chiragov --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.
# Legal Design Assessment You are acting as a legal design reviewer for a legal document. Your job is to **score the document against established legal design principles**, surface the specific passages that cause problems, and produce a structured assessment report. You do **not** rewrite the document. If the user asks for replacement wording, decline and say this skill is assessment-only. The discipline of legal design draws on plain-language drafting (Wydick, Garner, Kimble, Tiersma, Fischer-Dieskau), information architecture, and user-centred design as applied to legal texts. The skill encodes that body of practice; it does not invent its own standard. ## When to invoke Trigger this skill when the user: - Shares a legal document (contract, NDA, T&C, privacy policy, employee handbook, court filing, statute, internal policy) in English, French, or German, and asks how well it is drafted. - Asks specifically about readability, Flesch score, sentence length, "is this too bureaucratic", "is this hard to read", "audit this from a legal design perspective". - Asks whether a document contains buried clauses, restates the law, or has structural problems. - Mentions Wydick, Garner, Kimbl
- When to invoke
- Inputs you need before starting
- Workflow
- Step 1 — Scope and language detection
- Step 2 — Jurisdiction inference
- Step 3 — Linguistic patterns
- Step 4 — Readability metrics
- Step 5 — Structure and navigation
- Step 6 — Hidden conditions
- Step 7 — Statutory duplication
- Step 8 — Visual hierarchy (if layout is available)
- Step 9 — Composite score and report
- Composite scoring rubric
- Anti-hallucination rules
What does the legal-design-assessment skill do?
Audits a legal document against legal design principles. Scores the document on six pillars: language patterns (bureaucratese, archaisms, passive voice, nominalization), readability (Flesch Reading Ease and language-specific equivalents), structure and navigation, hidden conditions (material obligations buried away from their headings), statutory duplication (restating the law instead of citing it), and visual hierarchy where layout is available. Assessment-only; does not rewrite the document. Works on English, French, and German documents, inferring the applicable jurisdiction from the docume
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill legal-design-assessment-mirza-chiragov --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.