AugmentClaude

Plain Language Legal Writer

Simplify legal documents, contracts, and licenses using plain language standards.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/iso-24495-2-gazmagik/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Sector-specific Plain Language standard for legal communication (ISO 24495-2:2025). Applied during contract drafting, license review, and legal/compliance writing.

What this skill does

ISO 24495-2:2025 - Plain Language (Legal Communication)

Extends ISO 24495-1:2023 for legal documents, contractual provisions, licenses, and regulatory compliance.

Scope & Execution Boundaries

  1. Thinking Block Exemption:

    • Internal reasoning and legal analysis within thinking blocks (<thought>, <thinking>) are 100% exempt from plain language constraints.
    • Reason exhaustively within thinking blocks. Apply plain language rules strictly to final user-facing legal text.
  2. Legal Enforceability Primacy:

    • Plain language simplification must never alter legal rights, liabilities, or contractual enforceability. If a term of art is legally required to avoid ambiguity, retain it and provide a plain explanation.

Quantitative Rules & Hard Constraints (User-Facing Output)

  1. Modal Verb Standardisation:

    • Use must for mandatory obligations ("The User must pay...").
    • Use must not for prohibitions ("The User must not copy...").
    • Use may for discretionary permissions, as in "the User may end the agreement".
    • Banned Words: Never use "shall", "should", "hereby", "hereinafter", "wherefore", or "parties of the first part".
  2. Explicit Subject Actor Identification:

    • Every obligation sentence MUST explicitly name the subject actor ("The Licensee must notify..." rather than "Notice must be provided...").
  3. Conditional Clause Formatting:

    • Format multi-condition legal clauses as structured itemised lists:
      • Trigger / Prerequisite: What condition initiates the rule.
      • Obligation / Action: What action must or may be taken.
      • Consequence: What occurs upon non-compliance.

Contrastive Examples

Example 1: Contractual Obligation

  • Not aligned (Archaic Legalese):
    The Licensee shall hereinafter hold harmless and indemnify the Licensor
    from and against any and all claims wherefore notice has not been provided
    within thirty (30) days.
    
  • ISO 24495-2 Aligned:

    Indemnification Notice Requirement:

    1. Notice deadline: The Licensee must notify the Licensor of any claim within 30 days.
    2. Consequence: If the Licensee fails to meet this deadline, the Licensee must cover all resulting losses and legal costs incurred by the Licensor.

Pre-Output Self-Audit Checklist

Before outputting legal text, audit against these checks:

  • No legalese: Are terms like "shall", "hereinafter", and "hereby" eliminated?
  • Modal verbs: Are obligations expressed using only must, must not, or may?
  • Explicit subjects: Is every obligation attached to a clearly named actor?
  • Structured clauses: Are complex conditions presented in bulleted lists?
  • Legal accuracy: Is legal enforceability preserved?

Related skills