Agent skill · Content & Marketing

legal-document-drafting-formatting-alessandro-dardano

Produces properly-formatted legal documents in Word (.docx). The user provides the substantive content (instructions, attached files, project knowledge); the skill handles document architecture and formatting. * No precedent or template required * Seven document families: agreements, corporate documents, litigation, memos, employment, policies, correspondence * Jurisdiction-agnostic — works across any legal system the user specifies * Multi-Chain numbering, defined-terms convention, structured recitals, atomic signature blocks * Also reformats existing .docx to a consistent house style * Work

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill legal-document-drafting-alessandro-dardano --agent claude-code

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

Facts
Files in the skill folder: 3
SKILL.md size: 35 KB
Bundled scripts: none
Version: 2026-06-03
Declared author: Alessandro Dardano
Path: skills/legal-document-drafting-alessandro-dardano/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.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Produces properly-formatted legal documents in Word (.docx). The user provides substantive content; the skill handles document architecture and formatting across seven families, with jurisdiction-agnostic rules and multi-Chain numbering, defined-terms, structured recitals, and atomic signature blocks. It can also reformat existing .docx to a consistent house style. Works in Claude.ai, Cowork, and Claude for Word.

How it works

Two-layer approach: Layer 1 universal formatting (typography, margins, footer, signature blocks, entity verification) and Layer 2 document-family tracks (A through G) that apply the right structure. Document family is identified from the user’s request; tracks determine structure (Track A for transactional, Track B corporate, Track C litigation, Track D memo, Track E employment, Track F policy, Track G letter). When drafting from scratch, Layer 1 + Layer 2 + jurisdiction profile apply. If reformatting an uploaded document, the track is applied as a transformation: substantive content preserved, formatting converted to track conventions (typography, numbering, signature blocks, defined-terms, jurisdiction profile).

When to use it

Always when producing a .docx file for the Company.

What it can touch

Not specified inFACTS; tool access is listed as Claude Code. The skill references MC template and optional assets for formatting, numbering, and house-style application.

Caveats

Disclaimer notes that substantive content remains the responsibility of qualified counsel; the template is deployer-supplied and optional. The skill is jurisdiction-neutral by design, with starter profiles for NL, EN, HU, IT, PL; custom profiles can be added. If no profile is available, options include supplying a profile, proceeding with universal MC structure, or using a neighboring profile with flags.

From the SKILL.md

# In-House Counsel Document Format — Multi-Track House Style *Author: Alessandro Dardano. Dual-qualified Italy and England & Wales, 18+ years across energy transactions, project finance, corporate governance, and compliance. Originally developed for in-house use, generalised for publication.* *Version 2.3 — restructured for progressive disclosure: this SKILL.md is now a lean router, and the detailed material lives in `references/` modules that are read only when relevant. The MC template is a **deployer-supplied, optional** asset (`assets/inhouse-mc-template.docx`); where it is absent, MC tracks fall back to docx-js native automatic numbering (Environment 2). v2.3 corrects the earlier text that implied the template was bundled, aligns the `assets/` README accordingly, and adds a reformatting note on numbering that is itself cross-referenced (e.g., lettered article inserts). Substantive drafting content is unchanged from v2.1.* *Licensed under Apache 2.0. © 2026 Alessandro Dardano. See LICENSE file for terms.* > **Disclaimer.** This skill encodes document drafting and formatting conventions. It is not legal advice. Substantive legal content (clause selection, position, commercial te

What's inside
Steps it walks through
  1. Purpose
  2. Terminology
  3. Jurisdiction Architecture
  4. How it works
  5. Starter jurisdiction profiles (worked examples)
  6. Adding a jurisdiction profile
  7. What to do when no profile is available
  8. Role and Orientation
  9. When This Skill Applies
  10. Two distinct invocations
  11. How this skill is organised
  12. Layer 1 — Universal formatting (summary)
  13. Track selection (do this first)
  14. Workflow at a glance
Ships with 2 files
  • README.md
  • demo/demo-loi-ma-acquisition-uk.docx
More from awesome-legal-skills
All skills →
About this skill
What does the legal-document-drafting-formatting-alessandro-dardano skill do?

Produces properly-formatted legal documents in Word (.docx). The user provides the substantive content (instructions, attached files, project knowledge); the skill handles document architecture and formatting. * No precedent or template required * Seven document families: agreements, corporate documents, litigation, memos, employment, policies, correspondence * Jurisdiction-agnostic — works across any legal system the user specifies * Multi-Chain numbering, defined-terms convention, structured recitals, atomic signature blocks * Also reformats existing .docx to a consistent house style * Work

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill legal-document-drafting-alessandro-dardano --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