ambiguity-report
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," "
npx skills add lawve-ai/awesome-legal-skills --skill ambiguity-report-seth-chandler --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. - **Stage 1 — Identify the input.** Determine what kind of analysis the user is handing over. Three common shapes: (a) the structured markdown output of the `ambiguity-stress-tes
- Workflow
- Stage 1 — Identify the input
- Stage 2 — Build the canonical spec
- Stage 3 — Choose the format and design
- Capability check — do this first
- The six options
- Stage 4 — Render
- Output organization
- What this skill does not do
- When the user asks for design tweaks
- Bundled resources
- Limitations and risks
python scripts/generate_site.py \ python scripts/generate_latex.py \
What does the ambiguity-report skill do?
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," "
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill ambiguity-report-seth-chandler --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.