← Back to Lexa
AgentLexa
Verify primary legal sources
Checks legal requirements against authoritative text, applicable dates and the actual force of each source.
primary-legal-source-verification
See how it helpsWhen is it useful?
Use when a legal analysis or draft depends on a rule that may be outdated, transitional or merely advisory.
What does it help you do?
- Prioritizes legislation, binding decisions and official guidance.
- Separates entry into force from application dates and proposed rules.
- Labels mandatory duties, default rules, interpretations and company policy distinctly.
Try asking this
Verify the sources behind our AI disclosure requirements, recording applicability dates and questions that need legal interpretation. For each claimed duty, provide the official provision, relevant date and product trigger. Mark interpretation questions explicitly instead of presenting draft guidance as binding law.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Primary Legal Source Verification
Base every legal requirement and compliance claim on verified primary legal sources and official supervisory guidance. Never invent statutes, articles, regulatory opinions, or court rulings, and never cite a source whose relevant text you have not verified.
Source Hierarchy & Verification Protocol
- Prioritize Primary & Authoritative Sources:
- Primary legislation: Official statutory repositories (EUR-Lex for EU regulations/directives, official national gazettes and consolidated legislative databases).
- Binding decisions & case law: CJEU rulings, national supreme/constitutional courts, and binding supervisory decisions (EDPB binding decisions, Commission Implementing Decisions on SCCs or Adequacy).
- Official supervisory guidance: EDPB guidelines and recommendations, national data protection authorities (NAIH, BfDI/DSK, CNIL, ICO), consumer protection authorities, and AI Office guidance.
- Verify Temporal Validity & Scope:
- Check the consolidation date, entry into force, application date, and any transitional or phased-in provisions (such as staggered application dates under the EU AI Act or national transposition deadlines for EU directives).
- Distinguish clearly between:
- Currently enforceable law
- Adopted law in a transitional period (noting the exact application date)
- Proposed or draft legislation
- Classify Normative Force:
- For every requirement, record whether it is:
- Mandatory statutory rule (cannot be waived by contract)
- Default statutory rule (applies unless validly modified, e.g., in B2B contracts)
- Supervisory authority interpretation / best practice
- Commercial or operational policy choice
- For every requirement, record whether it is:
Source Citation Record
In the internal source register, record for each substantive requirement:
- Instrument & exact provision: Official title, number, and exact article/paragraph/point.
- Jurisdiction & scope: EU/EEA, specific Member State, UK, US state, and whether directives require national transposition check.
- Verification date & status: Date checked and current entry-into-force status.
- Product mapping: Which product feature, data flow, or document clause the provision governs.
Guardrails
- Never treat secondary blog posts, marketing summaries, or another company's privacy policy as a primary legal source; use them only as search leads to locate the statute or official guidance.
- When statutory interpretation is unsettled or depends on national case law nuances, state the uncertainty transparently and formulate a focused question for qualified legal counsel.
Included files 1
SKILL.md
