| name | eidas |
| description | eIDAS (Electronic Identification, Authentication and Trust Services) compliance checklist. Validates electronic identity, qualified signatures, trust services, and KYC/AML workflows. Use for banking KYC, digital onboarding, remote identification, and electronic signatures in the EU. |
| license | MIT |
| compatibility | opencode, cursor, windsurf, cline, generic |
| metadata | {"audience":"reviewer, orchestrator, backend-dev, frontend-dev","phase":"review, planning"} |
eIDAS Compliance Skill
You are executing an eIDAS (Electronic Identification, Authentication and Trust Services) compliance assessment.
Scope: This skill applies to EU banking and financial services that use electronic identity, digital signatures, remote identification, or trust services for customer onboarding, KYC, or transaction authorization.
Applicability
This skill is required if the project:
- Uses electronic identity verification for customer onboarding (KYC)
- Accepts or issues qualified electronic signatures (QES)
- Provides remote identification services
- Uses digital certificates or trust services
- Operates a trust service provider (TSP) or qualified trust service provider (QTSP)
- Integrates with national eID schemes (e.g., DNIe, BankID, Itsme)
- Processes cross-border electronic identity from other EU member states
This skill is not required if the project uses only username/password authentication without any electronic identity or trust service.
Electronic Identification (eID)
Levels of Assurance
| Level | Description | When Required |
|---|
| Low | Self-asserted identity | Minimal risk operations |
| Substantial | Verified identity with evidence | Standard banking onboarding, KYC |
| High | Verified identity with rigorous evidence | High-risk transactions, QES issuance |
Requirements
Qualified Electronic Signatures (QES)
Requirements
Signature Types
Trust Services
Requirements
KYC / AML Integration
PSD2 API Authentication (eIDAS Certificates)
Code-Level Checks
eIDAS 2.0 (Future Considerations)
Report Format
# eIDAS Assessment Report
## Scope: [module/feature assessed]
## Date: YYYY-MM-DD
## Applicability: [Applicable / Not Applicable]
[reason]
## Findings
### Electronic Identification — [🔴|🟡|✅]
[findings]
### Qualified Electronic Signatures — [🔴|🟡|✅]
[findings]
### Trust Services — [🔴|🟡|✅]
[findings]
### KYC / AML — [🔴|🟡|✅]
[findings]
### PSD2 API Authentication — [🔴|🟡|✅]
[findings]
### Code-Level Checks — [🔴|🟡|✅]
[findings]
## Summary
- 🔴 Critical: X
- 🟡 Warning: Y
- ✅ Pass: Z
- **Status**: [COMPLIANT | PARTIAL | NON-COMPLIANT]
## Action Items
1. [priority action]
Rules
- QES is legally binding — treat it as equivalent to a handwritten signature
- Biometric data is sensitive — apply GDPR protections to biometric data
- Cross-border eID must be recognized — eIDAS 2.0 mandates interoperability
- Trust services must be qualified — only QTSPs can issue QES certificates
- KYC data is high-risk — protect it with the same rigor as payment data
- Cross-reference with GDPR — eIDAS data is personal data
- Cross-reference with PSD2 — eIDAS certificates authenticate TPPs
- Cross-reference with AML — KYC requirements overlap with AML