← Plugin catalog
Education & Research

LexAgent

SWIS v0.1.1

Dutch and EU law, sourced

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Search and read Dutch legislation
  • Search and read local regulations
  • Search and read Dutch and EU case law

Declared limitations

  • Write action the plugin does not offer
  • Law outside the Netherlands and the EU
  • Unrelated question

Not specified in the available declarations: pricing & account requirements.

Onboarding example

What does article 6:162 of the Dutch Civil Code say about unlawful acts? Quote the text.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 5, 2026. Package observed Nov 5, 2026.

View package source →

Description

From the marketplace listing

LexAgent gives ChatGPT the official texts of Dutch and EU law, so answers rest on the source instead of memory. It reads, straight from the government open-data services: - National legislation from wetten.overheid.nl, article by article and for any date (peildatum). - Local regulations of municipalities, provinces and water boards (APVs, verordeningen, omgevingsverordeningen). - Official publications: Staatsblad, Staatscourant, Gemeenteblad and parliamentary papers. - Dutch case law from Rechtspraak, by ECLI, court, area of law and date. - EU legislation and treaty articles from EUR-Lex, including consolidated versions and the Dutch implementing measures. - Case law of the Court of Justice of the EU, down to the numbered point, and Advocate General opinions. - Council information: proposals, motions with votes, decision lists and minutes of Dutch councils. Every document comes with a citation (article, ECLI or CELEX, version date) and a link to the official source. Two skills guide the work: Dutch legal research, and checking the legal claims in a document against the sources. LexAgent is read-only: it never changes anything at the sources or in your account. It provides legal information from public sources, not legal advice. A LexAgent account is required.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Oct 28, 2026. Last seen Nov 5, 2026.

Keywords

Files & skills

File archives

Plugin package7 files · 21.6 KBBrowse files →
Skill instructions
check-legal-claims2.83 KB

View saved version →

---
name: check-legal-claims
description: Check the legal claims in a document or text against the official Dutch and EU sources through LexAgent - a decision (besluit), objection (bezwaarschrift), contract, advice memo, letter or draft. Use when the user asks whether a text is legally correct, asks to verify or fact-check its legal statements or references, or asks "klopt dit?".
---

# Checking legal claims with LexAgent

Goal: for every legal claim in the text, a verdict that rests on the official source, so the user can
see at a glance what holds, what does not and what could not be checked.

## 1. List the claims

Go through the text and pick out each **legal claim**: a statement about what a rule says, requires or
allows, a reference to an article, regulation or ruling, a deadline or competence derived from law.
Facts about the case (names, dates, what someone did or plans) are not legal claims; skip them.
Quote each claim exactly as it appears, one sentence or clause at a time.

## 2. Verify each claim

For each claim, read the source that governs it with the LexAgent document tools, following the
`dutch-legal-research` skill: the article itself for the right peildatum, then case law where the
claim depends on interpretation. Check the reference too: an article number that moved or a
regulation that was repealed or replaced is a finding in itself.

Also check what a text must say but does not. For a decision (besluit) of a government body that is
at least:

- **Statement of reasons** (art. 3:46 and 3:47 Awb): the grounds and, where possible, the legal basis.
- **Objection clause** (art. 3:45 Awb): that objection or appeal is possible, the period, and the body
  to send it to. A wrong period is a claim to check; a missing body is an omission to report.

Report an omission as its own row, quoting the passage it should have been part of.

## 3. Give one verdict per claim

Use exactly one of these statuses:

| Status | Meaning |
|---|---|
| **Klopt** | The cited source supports the claim. |
| **Onjuist** | The cited source contradicts it. |
| **Twijfel** | Partly supported, depends on facts not in the text, or rests on a weaker source such as council information. |
| **Niet gevonden** | You searched the sources that should cover it and none supports it. |
| **Niet te controleren** | The governing source is not available through LexAgent (for example an omgevingsplan, or case law that is not in the open data). |

Klopt, Onjuist and Twijfel always carry the citation the document tool returned. Give a one- or
two-sentence explanation per claim in the language of the text, and for Onjuist the correct wording
or reference.

## 4. Report

Present a table (quote, status, explanation, source), followed by a short summary: the claims that
need attention first, then what could not be checked and why. Do not rewrite the user's document
unless asked.
dutch-legal-research3.76 KB

View saved version →

---
name: dutch-legal-research
description: Answer questions about Dutch and EU law from the official sources through the LexAgent tools - national legislation (wetten.overheid.nl), local regulations (APV, verordeningen), official publications, Rechtspraak case law, EUR-Lex legislation, CJEU case law and council information. Use whenever the user asks what Dutch or EU law says, whether something is allowed or required in the Netherlands, which rule applies to a municipality or water board, or asks for case law, an article text or a citation.
---

# Dutch legal research with LexAgent

LexAgent's tools return the official texts; their descriptions and the server instructions explain
the mechanics (which identifier each tool takes, paging, `search_within`). This skill is about the
method: which sources to read, in what order, and how to report what they say.

## 1. Frame the question

Settle before searching, and ask only when it changes which source applies:

- **Level**: rijk (national law), gemeente, provincie or waterschap (local regulation), EU, or a
  combination. A location-bound activity often falls under a municipality *and* a water board.
- **Peildatum**: the date the law should be read for. Default to today and say so; for a past event
  read the text as it stood then (`in_force_on`, `version_date`).
- **What the user needs**: the rule itself, how courts apply it, or why it was made (legislative
  history, council decisions).

## 2. Read the binding text first

1. Find the regulation (`legislation-search`, `local-regulation-search`, `eu-law-search`).
2. Read the article itself with the matching `*-document` tool. Never state what an article says
   from memory or from a search snippet.
3. For an EU directive, follow the Dutch implementing measures to the national text.
4. Then case law, where interpretation matters: Rechtspraak (`case-law-*`) for Dutch courts, CJEU
   (`eu-case-law-*`) for EU law. Read the relevant passage before citing a ruling.
5. Official publications (Staatscourant, Kamerstukken, Gemeenteblad) and council information explain
   provenance and intent. They are context, not the rule in force; say so when you rely on them.

Search one concept at a time and vary the term after a miss rather than repeating the same call. When
a source that should govern the question is not available (an omgevingsplan, unpublished case law),
say that plainly instead of concluding that no rule exists.

Rules move. When an article you expected reads "vervallen", or a topic clearly continues outside the
regulation you are reading, find where it went before answering: a municipality moved permits and
terrace rules from its APV into a Verordening fysieke leefomgeving or the omgevingsplan, a national
rule may now sit in the Omgevingswet. Read that regulation too, for the same peildatum, and say which
regulation each part of the answer comes from. When comparing two dates, compare every regulation that
held the rule on either date, not only the one that holds it today.

## 3. Answer

- Lead with the answer, then the basis.
- Cite every legal statement with the `citation` the document tool returned (article, regulation,
  ECLI or CELEX, and the date or version), and link the official URL it carries.
- Quote decisive wording verbatim and briefly; paraphrase the rest.
- Separate what the text says from your reading of it, and name open points: facts you would need,
  conflicting rulings, a consolidation without legal effect, a fallback version a tool reported.
- Answer in the user's language; keep Dutch legal terms (bestemmingsplan, ingebrekestelling) where a
  translation would lose precision.
- This is legal information from public sources, not advice on the user's own case. When the stakes
  call for it, suggest having a lawyer review the conclusion, once and without boilerplate.

Release notes

First release: Dutch and EU legislation, case law, local regulations, official publications and council information.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
Apache-2.0
Package author
SWIS
Keywords
See keywords
Listing translations
nl-NL
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Search and read Dutch legislation
  • Search and read local regulations
  • Search and read Dutch and EU case law
  • Search and read EU legislation
  • Search and read official publications
  • Search and read council information

Package observed Nov 5, 2026.

Technical details
First seen
Oct 28, 2026 · 18:00 UTC
Last seen
Nov 5, 2026 · 06:00 UTC
Collection status
Collected

plugin_asdk_app_6acf762aa4e08191a1c6d129894ae434

Download plugin data (JSON)