What problem does it solve? Issuing a Loyalty Card verifiable credential requires an exact claim path pointer definition for each credential format, and hand-writing these nested claim arrays for dc+sd-jwt, jwt_vc_json, and mso_mdoc is error-prone. This Skill provides the ready-to-use schema documents from the iGrant.io verifiable data registry so the credential definition matches the registry exactly. ## Core Features & Use Cases - Three format schemas: Provides the full 25-claim path pointer documents for dc+sd-jwt, jwt_vc_json, and mso_mdoc, covering credential, customer, loyalty_card, organization, and portfolio claim groups. - API integration guidance: Shows how to POST the claims array to the iGrant.io credential-definition endpoint with the correct vct, type, doctype, and validationPath per format. - Issuance interview: Walks through environment, format, issuance mode, revocation, signing, and trust-list decisions before any code is written. - Use Case: A retailer wants to issue loyalty cards to customer EUDI wallets showing points and miles balances. The agent uses this schema to create the credential definition, enables revocation and reissuance, and issues cards that holders can selectively disclose at the till. ## Quick Start Ask your agent to create a Loyalty Card credential definition on the iGrant.io OpenID4VC API using the dc+sd-jwt format with revocation enabled.
