agentsclimarketplace

Legal writing

Skill mblauberg/provenant/skills/legal-writing

Portable equal-primary Claude and Codex agent harness for a governed agentic SDLC

Install
npx -y skills add mblauberg/provenant --skill legal-writing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use for drafting, reviewing, condensing, or source-checking Australian legal documents (forms, affidavits, submissions and orders), legal decision overviews, or correspondence. Not for academic, engineering, or general prose; use its specialist.

SKILL.md

3.8 KB, 761 tokens by cl100k_base, as published. Nobody here has run it

Australian legal writing

General Australian legal style, document-shape and source-discipline layer. Stricter project and forum instructions override it. This is drafting assistance, not legal advice: verify current law, forms and procedure against official sources and retain qualified or human review for filing-facing work.

This skill is a specialization of the natural-writing hub: it owns jurisdiction, forum and filing-facing rules, and links to the hub for the Australian English default, the anti-AI taxonomy and the condense pass (see references/australian-english-house-style.md, references/legal-concision-and-anti-ai.md and references/forbidden-patterns.md for where each hub link applies). The Legal Function Test remains this skill's own claim-classification scheme; it does not map to the hub's observed/inferred evidence schema.

Workflow

  1. Read project instructions, live matter state and source-boundary rules. Load the matching jurisdiction, forum and document skill where one exists.
  2. Choose draft, rewrite, condense, diagnose, correspondence, decision-overview or final-scrub. Load legal concision for all prose; the reference map in validation-checklists.md gives the remaining reference each mode or content type needs. For decision-overview, load decision overviews directly.
  3. Classify each sentence by legal function before polishing. Affidavits and witness statements give evidence; submissions argue; orders command; chronologies organise; internal notes analyse; correspondence communicates. Move wrong-home material first.
  4. Lock legal status, source anchors, exact quotations, authorities, labels, offer terms, non-admission/non-waiver wording, deadlines, attachments, redactions and user-authority conditions.
  5. Draft the minimum complete text in Australian English. Front-load the relief, request, answer or next step; use one proposition per paragraph, one home per point and exact pinpoints. Cut padding, duplicate history, intensifiers and internal agent language.

Every filing-facing fact needs a verified real source anchor. Never humanise by weakening a threshold, deleting an anchor, casualising court language or changing forum wording.

Never invent or silently alter an authority, instrument, finding, rule title, forum term or decision-maker label. Verify canonical sources, not indexes, summaries, OCR, renders or agent notes. Preserve contentions as contentions and hold the register required by the procedural stage. Protective-order, police-issued or other safety material remains a dated source with the legal effect its verified text supports; do not convert it into a finding. Keep source files, renders, OCR/transcripts, field maps and QA reports separate.

For substantial condensation or relocation, run the deterministic token set-diff and an independent qualitative pass. Stop before losing an anchor, qualification, disputed status, redaction, label, amount, date, forum wording or authority condition. Final scrub adds no new argument, fact or authority. It adds no history or courtesy closer unless legally necessary.

python3 "${AGENTS_HOME:-$HOME/.agents}/skills/legal-writing/scripts/lint_legal_style.py" path/to/source

Lint is a guardrail; source checks, forum skills, render checks and user gates still apply. Changes to filing-facing, source-boundary or lint rules require the owning harness's independent review gate.

Gives 0 of the 12 instructions most docs writing skills give in 761 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-06

  • announce the skill at startin 54 of 1637, across 21 files
  • convert legacy doc files before editingin 45 of 1637, across 7 files
  • predict questions readers might askin 42 of 1637, across 3 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test document with fresh context-less instancein 42 of 1637, across 3 files
  • ask interview questions one at a timein 42 of 1637, across 26 files
  • include exact file paths in every taskin 42 of 1637, across 15 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 1 file

Said here and by no other author read

  • read project instructions and source-boundary rules first
  • load the matching jurisdiction, forum and document skill
  • load the legal concision reference for all prose
  • classify each sentence by legal function before polishing
  • move wrong-home material first
  • lock legal status, source anchors and exact quotations

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.