usecases/ticket-agent/server/SKILL.md
Browse events and complete delegated ticket bookings using wallet-based credential receive and presentation flows. Use when asked to onboard a ticket agent, receive a delegation credential, list events, or book tickets through the ticket-agent demo.
npx skillsauth add vidos-id/usecase-demos delegated-ticket-bookingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to operate delegated ticket booking.
Base URL: https://barely-certain-mammoth.ngrok-free.app
If the user provides another API URL, use that instead.
This API uses credential delegation. The agent must first receive a delegation credential over OID4VCI, then present that credential over OID4VP to complete protected booking actions.
For all credential operations, use openid4vc-wallet only. Do not write custom scripts, custom protocol handlers, or manual credential-processing code.
This skill is meant to be read and followed ad hoc in the current session.
If the user provides this file by URL or raw skill.md content, read it and follow its instructions for the current task.
Do not claim or imply that the skill is installed locally.
Tell the user to complete their own setup in the relevant events web application first:
Web app: https://eudi-usecase.demo.vidos.id/ticket-agent/
Web app guide: https://eudi-usecase.demo.vidos.id/ticket-agent/guide
After those steps, the agent is ready to receive the delegation credential.
Install the CLI from https://github.com/vidos-id/openid4vc-tools.
Use the latest version of @vidos-id/openid4vc-wallet-cli.
openid4vc-wallet is the only approved way to receive, store, and present credentials for this skill.
npm install -g @vidos-id/openid4vc-wallet-cli
// OR
bun install -g @vidos-id/openid4vc-wallet-cli
openid4vc-wallet --help
Reference commands:
openid4vc-wallet init --wallet-dir ./wallet
openid4vc-wallet receive --wallet-dir ./wallet --offer "<openid-credential-offer://... or HTTPS offer URL>"
openid4vc-wallet present --wallet-dir ./wallet --request "<openid4vp://... authorization URL>"
./wallet, initialize it once with openid4vc-wallet init --wallet-dir ./wallet, and reuse it across the full flow.openid-credential-offer:// link, then receive the credential with openid4vc-wallet receive --wallet-dir ./wallet --offer "<offer>".GET /api/events and event details with GET /api/events/:id.POST /api/bookings and body { "eventId": "evt-001", "quantity": 2 }.authorizeUrl and statusToken from the booking response.openid4vc-wallet present --wallet-dir ./wallet --request "<authorizeUrl>".GET /api/bookings/status/<statusToken> every 3 seconds for up to 180 seconds.confirmed: booking succeededrejected: verification failed, report errorMessageexpired: verification session expirederror: report errorMessageopenid4vc-wallet exclusively for all credential operations.openid4vc-wallet supports the flow.openid4vc-wallet receive for delegation credential intake and openid4vc-wallet present for booking authorization.authorizeUrl with openid4vc-wallet present.https://eudi-usecase.demo.vidos.id/ticket-agent/event-images/<event-id>.tools
# Wine Store API Skill Use this skill to shop from the demo wine store over plain HTTP. **Base URL:** `https://mcp-wine-agent.demo.vidos.id` This API is session-based. Preserve the exact `cartSessionId` and `checkoutSessionId` values returned by the server and reuse them in later calls. ## Ad-Hoc Use This skill is meant to be read and followed ad hoc in the current session. If the user provides this file by URL or raw `skill.md` content, read it and follow its instructions for the current
tools
# Car Rental API Skill Use this skill to operate the demo car-rental concierge over its regular HTTP API. **Base URL:** `https://mcp-car-rent.demo.vidos.id` If the user provides another car-rental API URL, use that instead. This API is session-based. Preserve the exact `bookingSessionId` returned by the server and reuse it in later calls. Do not probe the `/mcp` endpoint for any reason, for the purposes of this skill only the regular HTTP API endpoints under `/api/...` should be used. ## Ad
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.