Agent skill · Data & Analytics

regulatory-deal-card-generator-patrick-munro

Generates standalone interactive HTML "deal cards" that translate complex regulations into negotiation-ready reference tools, systematically distinguishing mandatory obligations from negotiable implementation choices. Use when the user needs an interactive regulatory guide for (1) contract negotiation support, (2) client education or internal training, (3) regulatory briefings for commercial stakeholders, or (4) structured comparison between required and flexible compliance paths. Primary focus on EU digital regulation (Data Act, AI Act, CRA, DORA, NIS2, GDPR) but the structural pattern transf

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill regulatory-deal-card-generator-patrick-munro --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 8 KB
Bundled scripts: none
Version: 2026-04-25
Declared author: Patrick Munro
Path: skills/regulatory-deal-card-generator-patrick-munro/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Regulatory Deal Card Generator ## Purpose Produces a single self-contained HTML file that presents a regulation as an interactive "deal card" for use in negotiation, advisory, or training settings. The output clearly separates what the law compels from what it leaves open to the parties. This matters because most regulatory guides collapse the two together, which wastes negotiation capital on obligations that are not negotiable and leaves genuine flexibility on the table. ## When to use - Preparing for a contract negotiation where a specific regulation drives material clauses - Briefing a commercial counterparty or client on what a regulation actually requires of them - Building internal training material that needs to outlast a single briefing session - Producing a client-facing deliverable that survives being emailed around without losing its structure - Any situation where the question "must we, or may we?" needs to be answered clause-by-clause ## Output format A single HTML file, inline CSS and JS, no external dependencies beyond optional web fonts. Offline-capable. Print-friendly. Designed to be opened in a browser and used as a working tool, not a static reference. Core vis

What's inside
Steps it walks through
  1. Purpose
  2. When to use
  3. Output format
  4. Core structural rule
  5. Workflow
  6. Design principles
  7. Negotiation-focused framing
  8. Article-level precision
  9. Example-rich rows
  10. Severity framework
  11. HTML template
  12. Bilingual output
  13. Quality checklist
  14. Limitations and disclaimers
Ships with 3 files
  • LICENSE.txt
  • README.md
  • references/html-template.md
More from awesome-legal-skills
All skills →
About this skill
What does the regulatory-deal-card-generator-patrick-munro skill do?

Generates standalone interactive HTML "deal cards" that translate complex regulations into negotiation-ready reference tools, systematically distinguishing mandatory obligations from negotiable implementation choices. Use when the user needs an interactive regulatory guide for (1) contract negotiation support, (2) client education or internal training, (3) regulatory briefings for commercial stakeholders, or (4) structured comparison between required and flexible compliance paths. Primary focus on EU digital regulation (Data Act, AI Act, CRA, DORA, NIS2, GDPR) but the structural pattern transf

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill regulatory-deal-card-generator-patrick-munro --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.

Keep going