verified-email

Retrieve cryptographically verified user email from Android via Credential Manager Digital Credentials.

Updated May 22, 2026
One-click install
npx skills add https://github.com/ekawijayasusilo/kmp_template --skill verified-email-ekawijayasusilo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verified-email
Source: https://github.com/ekawijayasusilo/kmp_template/tree/main/.claude/skills/verified-email
Command: npx skills add https://github.com/ekawijayasusilo/kmp_template --skill verified-email-ekawijayasusilo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It reduces account sign-up and recovery friction by enabling users to retrieve a cryptographically verified email from their device without manual OTP or magic-link verification.

Core Features & Use Cases

  • Credential Manager verified email retrieval (Android client): Uses Credential Manager Digital Credentials with an OpenID4VP flow to fetch verified user attributes for secure identity use cases.
  • OpenID4VP request construction & response handling: Builds the required request JSON (including nonce and dcql_query claims) and extracts the returned credential JSON for parsing.
  • Server-side verification guardrails: Ensures the client performs only preliminary parsing while requiring full cryptographic validation on the backend using issuer/signature and nonce to prevent replay and spoofing.

Use Cases: account creation (sign-up), account recovery, and reauthentication for sensitive actions (all within an Android app client).

Quick Start

Ask an AI to generate an Android Credential Manager implementation that constructs the required OpenID4VP request JSON for UserInfoCredential, calls getCredential(), extracts credential.credentialJson, and outlines the exact server-side validation steps and required parameters (including nonce) for secure account provisioning.

Frequently Asked Questions about verified-email

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a verified email from an Android device using Credential Manager without OTP?

You can retrieve a cryptographically verified email from an Android device using Credential Manager Digital Credentials via an OpenID4VP flow. This constructs a request JSON with a cryptographic nonce and parses the returned DigitalCredential response to remove OTP-based friction.

What is the OpenID4VP request structure for Digital Credentials in Android?

The OpenID4VP request structure requires building a JSON payload that includes a per-request cryptographic nonce and dcql_query claims for UserInfoCredential. This request is passed to getCredential() to fetch verified user attributes securely.

Can I fully validate a Digital Credential response entirely on the Android client?

No, the Android client performs only preliminary parsing of the returned credential JSON. You must pass the raw responseJsonString plus the nonce to a backend server for full issuer, signature, and presenter validation to prevent replay and spoofing attacks.

Does Android Credential Manager support OpenID4VP for account recovery and sign-up flows?

Yes, Android Credential Manager supports OpenID4VP for account creation, account recovery, and reauthentication scenarios. It uses GetDigitalCredentialOption requestJson to satisfy Digital Credentials Verifier API integration requirements for secure account provisioning.

Why does my OTP-less verified email flow require a cryptographic nonce?

A per-request cryptographic nonce is required to ensure nonce integrity during server-side validation. Passing the nonce alongside the responseJsonString to your backend prevents replay attacks and ensures the credential presentation is fresh and cryptographically valid.