What problem does it solve? Building an OpenID4VP presentation definition that asks an EUDI Wallet for Person Identification Data (PID) requires exact claim paths per credential format, and the claim names differ between dc+sd-jwt, jwt_vc_json, and mso_mdoc. This Skill supplies the verified claim lists, vct/doctype identifiers, and API call patterns so the request is correct the first time. ## Core Features & Use Cases - Format-specific claim templates: Full claim lists for dc+sd-jwt (vct urn:eu.europa.ec.eudi:pid:1), jwt_vc_json, and mso_mdoc (doctype eu.europa.ec.eudi.pid.1), covering name, birth date, address, contact, and age-over claims. - iGrant.io API integration: Step-by-step creation of a presentation definition via POST /v2/config/digital-wallet/openid/sdjwt/presentation-definition and sending the verification request via the V3 send operation. - Use Case: Build an age-verification check that requests only the is_over_18 claim (SD-JWT VC) or age_over_18 element (mso_mdoc) from an EUDI Wallet, without exposing the holder's birth date. ## Quick Start Ask your agent to build an OpenID4VP presentation definition that requests the PID age-over-18 claim from an EUDI Wallet using the iGrant.io verifier API.