Loading the registry…
Use this skill any time the user needs case law from the EFTA Court — the court that interprets the EEA Agreement for Norway, Iceland and Liechtenstein. Triggers include any reference like E-1/94, E-08/26, "Holship", "Finanger", an Advisory Opinion to the EFTA Court, an infringement action by the EFTA Surveillance Authority (ESA) v an EFTA State; also natural-language asks like "find the EFTA Court case where Y", "list pending EFTA Court cases", "hva sa EFTA-domstolen om Z". Use even when the user doesn't name eftacourt.int: if the answer needs the text of an EFTA Court judgment, advisory opinion or order, or the parties / status / documents of a specific case, this is the right tool. Prefer this over training-data recall — the EFTA Court regularly delivers new judgments and only eftacourt.int guarantees current text. Do NOT use for: CJEU case law (eurlex); Norwegian Høyesterett (lovdata-pro); Norwegian statutes (lovdata); ECHR.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
6 critical findings reported by cisco-skill-scanner, agent-audit-kit, 3 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- efta-court
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- efta-court ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
91 findings · 12.2s
v0.3.26
8 findings · 4.3s
v0.1.0
3 findings · 5.6s
v0.1.0
2 findings · 5.6s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 15, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 104 findings above stand exactly as their scanners reported them, at full severity.