Agent skill · AI & Agents

legal-analysis-forge-oliver-schmidt-prietz

EU Digital Regulation Legal Analysis Forge — generates a tailored expert prompt for structured legal analysis of an EU digital-regulation document, optionally executes it in-session, and always produces a plain-English explainer alongside the formal output. Handles Regulations, Directives, Commission Guidelines, EDPB Opinions, CJEU and AG judgments, national DPA decisions, codes of conduct, and draft consultations across the EU digital stack.

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill legal-analysis-forge-oliver-schmidt-prietz --agent claude-code

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

Facts
Files in the skill folder: 7
SKILL.md size: 16 KB
Bundled scripts: none
Version: 2026-06-09
Declared author: Oliver Schmidt-Prietz
Path: skills/legal-analysis-forge-oliver-schmidt-prietz/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

# Legal Analysis Forge A prompt generator for structured legal analysis of EU digital regulation documents. The skill characterises a document, elicits the desired outcome and audience, and produces a tailored expert prompt. It optionally runs the prompt in-session and supports refinement. ## When to invoke Invoke when the user: - Provides a legal document (PDF, URL, pasted text) from the EU digital regulation stack and asks for analysis, feedback, a memo, a consultation response, a post, a briefing, or similar - References a recent EU instrument, judgment, or guidance document and signals they want structured analysis rather than a quick answer - Asks for an "effective prompt" for legal analysis of a specific document - Is preparing a stakeholder consultation response, a board paper, a client memo, or a horizon-scan entry on a regulatory development Do not invoke when: - The user wants a quick factual answer about a regulation. Answer directly. - The work is operational compliance (running an LIA, drafting a DPA, mapping AI Act obligations, building a RoPA). Route to the relevant compliance skill instead. - The document is outside the EU digital regulation scope. Decline and expla

What's inside
Steps it walks through
  1. When to invoke
  2. Scope
  3. Workflow
  4. Step 1 — Ingest
  5. Step 2 — Characterise
  6. Step 3 — Elicit
  7. Step 4 — Generate prompt
  8. Step 5 — Execute (optional)
  9. Step 6 — Refine
  10. Live research protocol
  11. When live research is offered
  12. Authoritative sources
  13. Procedure
  14. Freshness check (automatic for drafts)
Ships with 6 files
  • LICENSE.txt
  • README.md
  • evals.json
  • references/analytical_canon.md
  • references/document_taxonomy.md
  • references/outcome_templates.md
More from awesome-legal-skills
All skills →
About this skill
What does the legal-analysis-forge-oliver-schmidt-prietz skill do?

EU Digital Regulation Legal Analysis Forge — generates a tailored expert prompt for structured legal analysis of an EU digital-regulation document, optionally executes it in-session, and always produces a plain-English explainer alongside the formal output. Handles Regulations, Directives, Commission Guidelines, EDPB Opinions, CJEU and AG judgments, national DPA decisions, codes of conduct, and draft consultations across the EU digital stack.

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill legal-analysis-forge-oliver-schmidt-prietz --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