hlr-24-user-identification-in-proximity-scenari

Define EUDI high-level requirements for proximity user identification via device retrieval per ISO/IEC 18013-5.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-24-user-identification-in-proximity-scenari
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hlr-24-user-identification-in-proximity-scenari
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/hlr-24-user-identification-in-proximity-scenari
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill hlr-24-user-identification-in-proximity-scenari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the requirements for user identification within proximity scenarios, ensuring secure and standardized data exchange between EUDI Wallet Units and Relying Parties.

Core Features & Use Cases

  • Proximity Flow Support: Enables Wallet Units and Relying Parties to support device retrieval as per ISO/IEC 18013-5 for presenting or requesting PID/attestation attributes.
  • Security Enforcement: Mandates user approval for attribute presentation and prohibits server retrieval for enhanced privacy and control.
  • Use Case: A user needs to present their digital ID to a ticket inspector at a train station using their EUDI Wallet. This Skill ensures the Wallet Unit securely transmits the necessary attributes via a proximity flow after user confirmation.

Quick Start

Use the hlr-24-user-identification-in-proximity-scenari skill to ensure compliance with user identification requirements in proximity scenarios.

Frequently Asked Questions about hlr-24-user-identification-in-proximity-scenari

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is EUDI proximity identification and when is it required?

EUDI proximity identification defines secure data exchange between EUDI Wallet Units and Relying Parties via device retrieval. It is required when presenting PID or attestation attributes locally, such as showing a digital ID to a ticket inspector.

How does device retrieval work for EUDI Wallet proximity scenarios?

Device retrieval in EUDI Wallet proximity scenarios operates according to ISO/IEC 18013-5, enabling secure local transmission of identification attributes. It mandates explicit user consent before presenting any attributes and strictly prohibits server retrieval to maintain privacy.

Does EUDI proximity identification support server retrieval of wallet attributes?

EUDI proximity identification does not support server retrieval of wallet attributes. It prohibits server retrieval entirely to enhance privacy and user control, mandating device retrieval instead so users must explicitly approve all attribute presentations.

How to ensure user consent during EUDI Wallet proximity flows?

To ensure user consent in EUDI Wallet proximity flows, this Skill mandates explicit user approval for attribute presentation during device retrieval. This requirement enforces privacy by preventing automatic data sharing via server retrieval.

Can I use ISO/IEC 18013-5 device retrieval for EUDI Wallet attestation presentations?

Yes, you can use ISO/IEC 18013-5 device retrieval for EUDI Wallet attestation presentations. This Skill defines the high-level requirements for proximity flows, ensuring secure PID and attestation attribute exchange between Wallet Units and Relying Parties.