← Legal Data HunterCONTENT HISTORY

Update to Legal Data Hunter

Snapshot Sep 30, 2026 · 22:47 UTC · version 2.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "resolve-citation",
  "description": "Turn a loose or messy legal citation (ECLI, CELEX, article number, case/docket number, or informal reference) into the exact verified document and a clickable source URL using the Legal Data Hunter MCP — never a guessed link. Use whenever you need to look up or verify a specific legal reference.",
  "included_files": [],
  "skill_md_contents": "---\nname: resolve-citation\ndescription: Turn a loose or messy legal citation (ECLI, CELEX, article number, case/docket number, or informal reference) into the exact verified document and a clickable source URL using the Legal Data Hunter MCP — never a guessed link. Use whenever you need to look up or verify a specific legal reference.\n---\n\n# Resolve Citation\n\nYou resolve a loose or messy legal reference to the exact document and a verified, clickable URL using the Legal Data Hunter MCP. You never guess or construct a URL.\n\n**Important**: You assist with legal workflows but do not provide legal advice.\n\n## When to use\n\nWhenever the user gives a specific legal reference — an ECLI, a CELEX number, an article number, a case/docket number, or an informal citation (\"Cass. com. 12 avr. 2023, n° 21-12345\", \"art. 6 GDPR\", \"Van Gend en Loos\") — and wants the exact source.\n\n## Workflow\n\n1. **Resolve.** Call `resolve_reference(reference, hint_country, hint_type)`. **Always pass `hint_country`** (and `hint_type` — `\"legislation\"` or `\"case_law\"` — when you know it): it roughly DOUBLES the resolution rate (~65% vs ~31%), because most citation forms are ambiguous across the jurisdictions in the corpus. You almost always know the jurisdiction from context — supply it. Normalize common user phrasing before resolving when the jurisdiction is clear; for example, an English request for \"Article 1240 of the French Code civil\" should be resolved as `Article 1240 du Code civil` with `hint_country=\"FR\"` and `hint_type=\"legislation\"`.\n   - `resolve_reference(\"ECLI:EU:C:1963:1\", hint_country=\"EU\", hint_type=\"case_law\")`\n   - `resolve_reference(\"art. 1240 code civil\", hint_country=\"FR\", hint_type=\"legislation\")`\n2. **Read it.** If you need the text, call `get_document(source, source_id, include_full_text=true)` on the resolved record.\n3. **Cite it — verbatim URL only.** Quote the URL from the API response exactly. **NEVER invent or construct a URL**: database URLs contain internal identifiers (ECLI, CELEX, LEGIARTI) that cannot be guessed; a plausible-looking guess returns a 404 and destroys reader trust. If `resolve_reference` returns only low-confidence candidates, present the best match and label it unverified. If it fully fails, fall back to Legal Data Hunter `search`, then consult reliable external sources, prioritizing official courts, legislatures, regulators, and gazettes. Clearly label externally verified sources and never present them as LDH results. If no reliable source can be verified, use a plain-text citation without a link.\n4. **Report gaps.** If a well-known reference fails to resolve, call `report_source_issue(source, issue_type=\"data_quality\", description=...)` including the exact failed call and why it should be resolvable.\n\n**Output:** the citation as an inline markdown link to the verified URL (jurisdiction, court/title, date, number), or plain text if unresolved. See the **legal-citations** skill for the full citation discipline and per-type examples.\n"
}

SHA-256: ba88b6efebab38a41d711d419c9859b8cb30f1b235950cb653ad4afa1f2d6449