Legal Legal Writing Editor

Provides structured frameworks, checklists, and templates to improve legal writing clarity, organization, argument structure, and reader-focused summaries.

Security Scan

This is a document-only, descriptive legal-writing workflow skill that requests no credentials, performs no installs, and its runtime instructions are consistent with the stated purpose.

Purpose & Capability

Name, description, SKILL.md, README.md, and skill.json all describe the same document-only legal-writing assistance (checklists, templates, prompts). There are no requests for unrelated capabilities such as cloud access, credentials, or code execution.

Instruction Scope

SKILL.md restricts the skill to collecting matter context, facts, audience, deadlines and producing checklists/templates and notes. It explicitly forbids code execution, network calls, database lookups, or automated filings. It does not instruct the agent to read unrelated system files or exfiltrate data.

Install Mechanism

No install spec and no code files are present (instruction-only). This minimizes on-disk risk and there are no download or extraction steps.

Credentials

The package declares no required env vars, no primary credential, and SKILL.md does not reference secrets or external APIs. The requested level of access is minimal and appropriate for a document-only skill.

Persistence & Privilege

Flags show always=false (not force-included). disable-model-invocation=false is the platform default and acceptable here. The package does not attempt to modify other skills or system settings.

Assessment

This skill is internally consistent and low-risk: it is purely document-driven, requests no credentials, and does not execute code or call external services. Before using, note that the package source/homepage is not provided (skill.json lists an author but provenance isn't verifiable), so treat it like community content rather than an official vendor release. Do not rely on its outputs as legal advice — verify citations, deadlines, and jurisdictional requirements with qualified counsel. Avoid pasting highly sensitive or privileged client data into any third-party skill unless you have an explicit, secure agreement and understand how your agent stores or logs user inputs.

Legal Writing Editor

Overview

Improves legal writing structure by organizing issues, arguments, headings, authorities, clarity, tone, and reader-focused summaries. This is a descriptive OpenClaw skill for legal-industry workflow support. It provides structured frameworks, checklists, templates, and issue-spotting prompts. It does not execute code, call external APIs, access legal databases, retrieve court records, automate filings, or perform legal services.

When to Use

• Revising memos, briefs, letters, or client updates
• Improving argument structure
• Making legal writing clearer for non-lawyers

Target Users

• Lawyers
• Legal writers
• Law students
• In-house counsel

Inputs to Collect

• Matter or project context, including jurisdiction if known
• Relevant facts, documents, parties, dates, and constraints
• Desired output format, audience, and level of detail
• Known deadlines, risk concerns, or review priorities

Core Modules

1. Issue-framing check — provides structured prompts, checklists, and review fields for this area.
2. Argument structure review — provides structured prompts, checklists, and review fields for this area.
3. Heading and roadmap builder — provides structured prompts, checklists, and review fields for this area.
4. Authority integration checklist — provides structured prompts, checklists, and review fields for this area.
5. Plain-English rewrite prompts — provides structured prompts, checklists, and review fields for this area.

Workflow

1. Confirm the user's legal workflow goal and the relevant practice context.
2. Ask for missing facts, documents, dates, parties, jurisdiction, and audience where needed.
3. Apply the modules below as a structured thinking framework.
4. Produce checklists, templates, matrices, memos, or planning aids tailored to the user's context.
5. Flag uncertainty, verification needs, deadlines, ethics concerns, confidentiality issues, and attorney-review points.

Expected Outputs

• Revision checklist
• Suggested outline
• Plain-English summary
• Tone and clarity notes

Example Prompts

• "Help improve the structure of this legal memo."
• "Turn this legal explanation into a clearer client update."

Safety and Legal Limitations

• This skill provides informational workflow support only and is not legal advice.
• It does not create an attorney-client relationship and does not replace review by a qualified attorney.
• Laws, court rules, deadlines, ethics duties, privilege, confidentiality, and professional responsibility rules vary by jurisdiction and matter.
• Users must verify all legal authorities, filing requirements, deadlines, facts, citations, and strategic decisions with qualified counsel.
• The skill must not be used to fabricate evidence, coach false testimony, evade regulation, access data unlawfully, or bypass confidentiality obligations.
• Specific limitation for this skill: Does not verify legal authorities or citations; users must confirm accuracy and ethics obligations.

Acceptance Criteria

• Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.
• SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.
• Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.
• Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.
• skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.