Igrantio dcql student pass
DCQL pattern: mandatory plus optional credential groups in one OpenID4VP verification on the iGrant.io Organisation Wallet Suite - a student transport pass requiring PID (mso_mdoc) plus Student ID or Enrolment Letter, with an OPTIONAL (required: false) residency group (Utility Bill or Rental Agreement) unlocking an extra discount. Shows required: false credential_sets for EUDI Wallet (EUDIW) verifiers under eIDAS 2.0.From its SKILL.md
npx -y skills add L3-iGrant/skills --skill igrantio-dcql-student-passAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.1 KB, 928 tokens by cl100k_base, as published. Nobody here has run it
DCQL: mandatory + optional groups (student transport pass)
Scenario
A transport authority sells a discounted student pass. Mandatory: PID
(identity) AND student status (Student ID card OR Enrolment Letter).
Optional (required: false): local-residency proof (Utility Bill OR
Rental Agreement) for an additional discount - the wallet presents it only
if the holder has and consents to it.
Before you build: run the integrator intake in igrantio-ows-overview - environment, API key, tenancy, backend host, webhooks, frontend - one question at a time, a recommended default with each.
The DCQL query
{
"credentials": [
{
"id": "pid",
"format": "mso_mdoc",
"meta": {
"doctype_value": "urn:eu.europa.ec.eudi:pid:1"
},
"claims": [
{ "id": "full_name", "path": ["full_name"] },
{ "id": "dob", "path": ["date_of_birth"] }
],
"claim_sets": [["full_name"], ["dob"]]
},
{
"id": "student_id_card",
"format": "dc+sd-jwt",
"meta": { "vct_values": ["student_id"] },
"claims": [
{ "id": "student_id", "path": ["student_id"] },
{ "id": "university_name", "path": ["university_name"] }
],
"claim_sets": [["university_name", "student_id"]]
},
{
"id": "enrolment_letter",
"format": "dc+sd-jwt",
"meta": { "vct_values": ["employment_letter"] },
"claims": [
{ "id": "status", "path": ["status"] },
{ "id": "university_name", "path": ["university_name"] }
],
"claim_sets": [["university_name", "status"]]
},
{
"id": "utility_bill_doc",
"format": "dc+sd-jwt",
"meta": { "vct_values": ["utility_bill_doc"] },
"claims": [{ "id": "address", "path": ["address"] }]
},
{
"id": "rental_agreement_doc",
"format": "dc+sd-jwt",
"meta": { "vct_values": ["rental_agreement_doc"] },
"claims": [{ "id": "address", "path": ["address"] }]
}
],
"credential_sets": [
{ "options": ["pid"], "required": true },
{ "options": [["student_id_card"], ["enrolment_letter"]], "required": true },
{ "options": [["utility_bill_doc"], ["rental_agreement_doc"]], "required": false }
]
}
Run it on OWS
- Store as a presentation definition; send the verification request (v3).
- On
presentation_acked+verified === true, the presentation holds 2 OR 3 credentials. Branch on whether the optional residency group came back (checkpresentationSubmission) and price the pass accordingly.
Adjust for your deployment
- The example
vct_valuesare pilot values (noteemployment_letterfor the enrolment letter) - pin them to your issuers' real VCTs. - Optional groups must change an OUTCOME (discount tier), never gate the flow; treat absence as the normal path.
- Trim claims to what pricing actually needs.
Cross-references
igrantio-dcql-kyc- the all-mandatory version of this pattern.igrantio-dcql-claim-sets- fallbacks within one credential.
Source of truth
This workflow mirrors https://docs.igrant.io/docs/dcql-2-4-5-student-transport-pass/ (query detailed in https://docs.igrant.io/concepts/eudi-wallet-dcql-openid4vp-business-wallet-payments/, §2.4.5). Before implementing, fetch the doc page; if it disagrees with this skill, the documentation wins - follow it and report the drift so the skill can be updated.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most education skills give in 928 tokens
Counted across 169 of the 171 authors here whose files we hold, read 2026-08-07
- Search for existing resources before creating new onesin 7 of 169, across 3 files
- Check tool responses for errors before proceedingin 7 of 169, across 3 files
- Reduce request frequency on rate limit errorsin 7 of 169, across 3 files
- Confirm connection status is ACTIVE before running workflowsin 7 of 169, across 3 files
- Execute prerequisite steps first in workflowsin 7 of 169, across 3 files
- Handle pagination by fetching until exhaustedin 7 of 169, across 3 files
- Re-authenticate if the connection expiredin 6 of 169, across 2 files
- Always call RUBE_SEARCH_TOOLS first to get schemasin 6 of 169, across 2 files
- Pass strictly schema-compliant tool argumentsin 6 of 169, across 2 files
- Run the skill generator if the shared file is missingin 6 of 169, across 3 files
- Create the coursein 5 of 169, across 3 files
- List enrolled studentsin 5 of 169, across 3 files
Said here and by no other author read
- run integrator intake one question at a time
- store the query as a presentation definition
- send the verification request
- check the verified status upon acknowledgement
- branch on the optional residency group outcome
- price the pass based on presented credentials
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.