What problem does it solve? Issuing a QESAC credential through the iGrant.io OpenID4VC API requires the exact claim path pointer structure from the verifiable data registry, and guessing the schema fields leads to credential definitions that verifiers reject. ## Core Features & Use Cases - Registry-Backed Schema: Provides the exact QESAC claim path pointer document for the dc+sd-jwt format, including the mandatory credentialId claim, vct value, and validationPath. - API Request Template: Supplies a ready-to-adapt JSON body for the POST /v2/config/digital-wallet/openid/sdjwt/credential-definition endpoint, with notes on labels, versioning, and multi-format entries. - Integrator Interview: Walks through environment, API key, format, issuance mode, revocation, signing, and trust-list decisions before any code is written. - Use Case: An integrator building an EUDI Wallet issuer backend uses this skill to create a QESAC credential definition on the iGrant.io demo environment with the correct claims array copied verbatim from the registry. ## Quick Start Ask your agent to create a QESAC credential definition on the iGrant.io demo environment using the dc+sd-jwt format with the registry claim path pointer.