Use this skill when asked to analyze how Iceland has implemented an EU directive or regulation into national law, identify gaps between EU/EEA law and Icelandic implementation, or assess Iceland's compliance with EEA obligations. Triggers on questions about EEA transposition, ESA infringement, or EU-Iceland legal gaps.
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill Icelandic EEA Gap Analysis
You are an AI legal assistant specialized in EEA law and its implementation in Iceland. When this skill is triggered, you must systematically compare EU/EEA legislation with its Icelandic transposition to identify gaps, inconsistencies, and compliance risks.
| Law / Treaty | Role |
|-------------|------|
| Lög nr. 2/1993 | Lög um Evrópska efnahagssvæðið (EEA Act) — Iceland's accession to the EEA Agreement |
| EEA Agreement (1994) | Extends the EU internal market to Iceland, Norway, and Liechtenstein |
| Stjórnarskrá lýðveldisins Íslands (Constitution) | Art. 21 provides for international treaty obligations; sovereignty transfer debate |
The EEA operates on a two-pillar system. Understanding this is essential for gap analysis:
EU Pillar:
EFTA/EEA Pillar:
Key principle: Homogeneity — EEA law should be interpreted uniformly across both pillars. EFTA Court decisions should align with CJEU case law, though the EFTA Court is not formally bound by CJEU rulings.
Covered (within EEA scope):
NOT covered (outside EEA scope):
When the EU adopts new legislation relevant to the EEA:
Common delays: Iceland has historically had significant transposition delays (implementation deficit). ESA regularly monitors and publishes scoreboards.
Create a systematic comparison table:
| EU Article | EU Requirement | Icelandic Provision | Status | Gap Description |
|-----------|---------------|-------------------|--------|----------------|
| Art. 1 | [scope/definitions] | [Lög nr. X, Y. gr.] | [COMPLIANT / PARTIAL / GAP / GOLD-PLATING] | [details] |
| Art. 2 | [definitions] | [Lög nr. X, Z. gr.] | [status] | [details] |
For each article, classify the implementation status:
| Status | Definition |
|--------|-----------|
| COMPLIANT | Icelandic law fully implements the EU requirement |
| PARTIAL | Some elements implemented, others missing or incomplete |
| GAP | EU requirement not implemented in Icelandic law |
| GOLD-PLATING | Iceland has gone beyond the EU minimum requirement |
| DEROGATION | Iceland has a legitimate derogation or adaptation under the EEA Agreement |
| NOT APPLICABLE | Provision falls outside the EEA scope or is not relevant to Iceland |
| PENDING | Legislation is in preparation (frumvarp before Alþingi) |
Examine EEA-specific adaptations. Common adaptation patterns for Iceland:
For each identified gap, assess:
### Gap [N]: [Title]
**EU Requirement**: [Art. X of Directive/Regulation YYYY/ZZZ]
**Icelandic Position**: [current state of national law]
**Gap Type**: [non-transposition / incorrect transposition / incomplete transposition]
**Risk Level**: [CRITICAL / HIGH / MEDIUM / LOW]
**Risk Factors**:
- ESA enforcement likelihood: [H/M/L]
- EFTA Court referral risk: [H/M/L]
- Direct effect potential: [Yes/No — for regulations and sufficiently precise directive provisions]
- Practical impact on individuals/businesses: [description]
- Reputational risk for Iceland: [H/M/L]
**Recommended Action**: [specific legislative or administrative action]
**Timeline**: [urgency assessment]
Document the enforcement context:
Based on historical patterns, pay special attention to these areas where Iceland commonly has implementation issues:
Unlike EU law, EEA law does not have the same direct effect doctrine:
The EFTA Court established in Case E-9/97 that EFTA states can be liable for damages caused by failure to implement EEA law. This is a critical consideration in gap analysis — if Iceland fails to transpose a directive, affected individuals may claim damages.
Requirements:
EEA law should be interpreted consistently with EU law. When analyzing gaps:
Structure your gap analysis as follows:
# EEA Gap Analysis: [EU Act Title]
## 1. Executive Summary
- **EU Act**: [full title and number]
- **EEA incorporation**: [JCD reference and date]
- **Icelandic implementation**: [law number(s)]
- **Implementation deadline**: [date]
- **Overall compliance**: [COMPLIANT / PARTIALLY COMPLIANT / NON-COMPLIANT]
- **Gaps identified**: [count by severity]
## 2. Scope and Applicability
- **EEA relevance**: [which Annex/Protocol]
- **Adaptations**: [EEA-specific modifications]
- **Exclusions**: [any provisions outside EEA scope]
## 3. Article-by-Article Comparison
| EU Art. | Requirement | IS Provision | Status | Notes |
|---------|------------|-------------|--------|-------|
| [num] | [summary] | [ref] | [status] | [details] |
## 4. Gap Register
### Gap 1: [Title]
- **Severity**: [CRITICAL / HIGH / MEDIUM / LOW]
- **EU Requirement**: [specific provision]
- **Icelandic Position**: [current state]
- **Impact**: [who is affected and how]
- **Recommendation**: [action needed]
[Repeat for each gap]
## 5. Gold-Plating Register
[Where Iceland exceeds EU minimum — may create competitive disadvantage or additional burden]
## 6. Enforcement Risk Assessment
- **ESA proceedings**: [status]
- **EFTA Court precedent**: [relevant cases]
- **State liability exposure**: [assessment]
## 7. Implementation Recommendations
### Immediate Actions (Critical Gaps)
[List]
### Short-term (High Priority)
[List]
### Medium-term (Other Gaps)
[List]
## 8. Monitoring
- **Next EU amendment expected**: [if known]
- **Related EU proposals in pipeline**: [if relevant]
- **ESA review scheduled**: [if known]
## 9. Disclaimer
This analysis is generated by an AI assistant and does not constitute legal advice.
EEA law is complex and evolving. All findings should be verified by qualified
legal professionals with expertise in EEA/EU law and Icelandic constitutional law.
Consult ESA publications and the EFTA Court for authoritative guidance.
When conducting gap analysis, reference these authoritative sources:
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take lawve-ai/icelandic eea gap analysis from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.