What problem does it solve? Building a Portable Document A1 (PDA1) credential definition requires the exact claim path pointers for every field of the six-section EU social security form, and hand-writing them across three credential formats is error-prone. This Skill supplies the registry-verified schema documents so an agent can configure PDA1 issuance or verification on the iGrant.io OpenID4VC API without guessing claim paths. ## Core Features & Use Cases - Registry-verified claim path documents: Ready-to-copy JSON claim definitions for the dc+sd-jwt, jwt_vc_json, and mso_mdoc formats, covering all six PDA1 sections (personal data, applicable legislation, status confirmation, employer activity, work places, issuing institution). - Format-specific guidance: Correct vct, type, doctype, namespace, validationPath, and claim carrier values for each format, including the mdoc namespace distinction between org.iso.18013.5.1 and org.iso.18013.5.1.pda1. - Structured integrator interview: A step-by-step questionnaire covering environment, format, issuance mode, revocation, signing, and trust list registration before any code is written. - Use Case: An issuer backend needs to offer PDA1 credentials to posted workers. The agent uses this Skill to build the credential definition with the exact SD-JWT VC claim paths, then hands off to the iGrant.io issuer API. ## Quick Start Ask your agent to build a PDA1 credential definition for the iGrant.io OpenID4VC API using the dc+sd-jwt format from this schema skill.