ThomasMoreAI/legal-skills-open / au/general/skills/informal-legal-voice-jakelawllm
informal-legal-voice-jakelawllm
VerifiedDrafts and revises short, plain Australian client messages for an established relationship and routine updates when an informal or conversational register is requested.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| SKILL.md | skill md | 7.4 KB |
| examples.md | markdown | 5.9 KB |
| references/legal-accuracy-and-court-rules.md | markdown | 7.1 KB |
| references/register-guide.md | markdown | 3.0 KB |
| references/style-audit.md | markdown | 6.7 KB |
references/style-audit.md
View on GitHub<!-- Generated from shared/style-audit.md. Do not edit this copy directly. -->
# Style audit
Run this audit before delivering. Accuracy comes before style: never let a stylistic rule change the law, the facts, or the source wording.
## Accuracy before style
- Preserve facts, legal meaning, and source wording.
- Do not change a term of art for a plainer synonym, and do not alter a defined term or vary a procedural label for the sake of variety.
- Do not sacrifice required legal analysis to brevity.
- Favour precision over reach. A rule that wrongly flags ordinary writing is worse than one that misses a tell, because a false flag teaches the writer to distrust every other rule. Where a flagged word is the precise and natural choice, leave it.
## Hard rules
These are firm rules, not preferences. The writing this skill produces must obey them, and so must this file.
- No negative parallelism. Do not write "it is not just X, it is Y", "not only X but also Y", "no X, no Y, just Z", the "X, not Y" appositive used for effect, or the two-sentence variant. State both facts plainly.
- Straight quotation marks and apostrophes only. Do not use curly or typographic marks, and do not mix the two in one document.
- Em dashes: no more than one per several paragraphs. Prefer a comma, parentheses, a colon, or a full stop and a new sentence.
- Do not routinely group descriptions into three-part lists. Vary the count; sometimes one item is enough.
- Do not cycle through synonyms for one referent. Repeat the name or a pronoun rather than reaching for a strained synonym.
- Do not use a "from X to Y" range where no real scale exists between the endpoints.
- Sentence-case headings, not title case, unless a style guide requires otherwise.
- Reserve bold for defined terms or headings. Never bold a phrase for emphasis inside a paragraph, and do not write a list where each item is a bolded label, a colon, and a sentence restating the label.
- No emoji unless the user uses them, requests them, or the channel and relationship clearly support them. Never on serious news.
- Vocabulary watch, first tier: avoid outright. These read as generated almost wherever they appear, so replace them: delve, tapestry, underscore, showcase, realm, embark, garner, testament, interplay, intricacies, captivating, majestic, leverage, leveraging, seamless, cornerstone, ecosystem (outside biology), navigate (figurative), landscape (figurative).
- Vocabulary watch, second tier: watch for clustering. Each is fine on its own and a tell in groups, so allow no more than one or two per thousand words and never two in the same paragraph: pivotal, intricate, foster, vibrant, nuanced, multifaceted, comprehensive, crucial, moreover, furthermore, additionally, notably, specifically, ultimately, aligns, facilitate, bolster, spearhead, robust, harness, meticulous, commendable, noteworthy, groundbreaking, innovative, devoid, fascinating.
- Each entry covers its variants (plural, "-ing", "-ly", comparative, and verb forms) unless a variant carries a distinct, legitimate meaning.
- Prefer the plain word: "use" over "utilise", "help" over "facilitate", "show" over "demonstrate". Prefer "is" and "are" over "serves as", "represents", and "constitutes" where you mean only that something is something; prefer "has" over "features", "offers", and "boasts". Keep a precise legal term, including "constitutes" or "commence", where it is the right word and the plainer synonym would be less accurate.
- Carve-outs. A watched word is fine where it is the precise term or carries a literal meaning: a physical "landscape", a vessel that "navigates", an "ecosystem" in biology, the "cornerstone" of a building, a statutory "commence" or "constitutes".
- Self-reference. Text that quotes or illustrates a banned pattern is exempt from it. A banlist, a rule that names a word, or a labelled example of poor writing may carry the very words and constructions being warned against. Audit the author's own prose, and leave quoted and illustrative material intact.
## Common drafting defects
Check for and cut:
- generic throat-clearing and stock openers ("I hope this email finds you well", "I am writing to", "further to the above");
- a paragraph that ends by restating its own opening, or by explaining why the preceding facts matter;
- abstract nouns hiding the actor, where a verb and a named agent would be clearer;
- unsupported adjectives and promotional or tourism language ("stands as a testament", "plays a vital role", "rich history", "must-visit", "vibrant");
- claims attributed to an unnamed authority ("industry reports suggest", "some critics argue", "it is widely regarded");
- mechanical transitions used more than twice on a page ("moreover", "furthermore", "additionally", "in contrast");
- a shallow participial clause at the end of a sentence that adds no information ("ensuring...", "highlighting...", "underscoring...");
- stock chatbot framing ("certainly!", "great question!", "I hope this helps!"), any line framing the deliverable ("Here is the letter:"), and any mention of being an AI or a training cutoff;
- invented specificity: a name, date, amount, or quotation that did not come from the user, the file, or a verified source;
- placeholder text in a final deliverable ("[insert name here]", "2025-xx-xx", "TBC", "xx/xx/xxxx") unless a template was requested;
- citation artefacts ("citeturn0search0", "oai_citation", "contentReference[oaicite:...]", "[web:1]") and tracking parameters in URLs.
## Natural prose
- Vary sentence length where the substance calls for it; if three sentences in a row run the same length, break the pattern.
- Use a list where it aids comprehension, and a table where a comparison is genuinely clearest, but do not build a table where a sentence would do.
- Keep the document's existing typography unless asked to change it.
- Use a synthesis sentence where it completes legal reasoning or explains practical effect.
- Do not insert awkwardness to seem human. Correct grammar, precise vocabulary, and standard letter conventions are not signs of AI writing.
- Do not use an AI-detection tool as the check; those tools produce false positives on formal and non-native English.
## Structural checks
Run these two checks on the finished draft. They catch the structural tells that surface-level edits miss.
- Paragraph-reshuffle test. If two body paragraphs can swap places without breaking the piece, the argument has no through-line. Give it an order where each paragraph depends on the one before.
- Information-density test. Read each paragraph and ask what it adds that the reader did not already have. Where a paragraph only restates an earlier point or sets up the next one, cut it or merge it.
## Australian English
Use Australian spelling and usage throughout (organise, defence, favour, recognise). Do not use US spelling or idiom.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |