Skills

Ambiguity Report

Turn an interpretive-ambiguity audit of a legal text, contract, statute, regulation...

Install

npx skills add lawve-ai/awesome-legal-skills --skill ambiguity-report -g -a claude-code -y
Category
Design
Updated
16d ago
License
See repository
Context cost
Mediumabout 3,000 tokens
Runs scripts
Yes, review before use

What it does

Turn an interpretive-ambiguity audit of a legal text, contract, statute, regulation, or judicial opinion, into a polished deliverable. Produces a multi-page website (default), a single-page interactive site, a Microsoft Word document, a PowerPoint deck, or a LaTeX/PDF. Use whenever a user has a stress-test result, ambiguity audit, or "where will this be litigated" scenarios and wants to publish, present, or share them. Triggers on "publish the audit," "make a report from this," "turn this into a website / deck / brief / Word doc," "make a Netlify site," "build slides of these ambiguities," "render the scenarios," "package this stress test," "produce a LaTeX version," and similar. Pairs with the ambiguity-stress-test skill (the underlying analysis) but works on any structured or semi-structured ambiguity analysis. Visual design is opinionated but the user can override colors, fonts, and brand label. Most formats need Python and a writable filesystem; single-file HTML works where the host has neither.

Ambiguity Report

Take an interpretive-ambiguity analysis of a legal text and turn it into a polished deliverable in one of six formats: multi-page website (the default), single-page interactive website, single-file HTML, Microsoft Word document, PowerPoint deck, or LaTeX source for a PDF.

Before promising a format, know what this host can do. Four of the six formats have requirements the host may not meet, and discovering that after the spec is built wastes the user's effort. Run the capability check in Stage 3 first.

The skill's central insight: the data is the same across formats, the rendering is not. An ambiguity analysis is a set of scenarios, each with a situation, two opposed positions, a weak point in the text, a likely outcome, and a proposed redraft, anchored to provisions of a source text. Once that data is captured in the canonical spec, the right format follows from how the deliverable will be used.

Workflow

This skill has four stages. Stages 1, 3 are setup; stage 4 is rendering.

Read the whole SKILL.md on GitHub

More in Design