verified-email

Retrieve verified emails on Android via Credential Manager and OpenID4VP.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/shirulot/codex-skill --skill verified-email-shirulot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verified-email
Source: https://github.com/shirulot/codex-skill/tree/main/verified-email
Command: npx skills add https://github.com/shirulot/codex-skill --skill verified-email-shirulot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires androidx.credentials:credentials, androidx.credentials:credentials-play-services-auth, and includes references (resource) components.

What problem does it solve?

This Skill solves the high-friction problem of traditional email verification by replacing manual OTP entry with cryptographically verified credentials, significantly improving user sign-up conversion rates.

Core Features & Use Cases

  • Credential Manager Integration: Implements the Android Credential Manager API to request and verify user identity attributes.
  • Cryptographic Validation: Provides a secure workflow for server-side verification of SD-JWT tokens and issuer authenticity.
  • Use Case: Use this during account creation or recovery flows to instantly verify a user's email address without requiring them to check their inbox for a verification code.

Quick Start

Use the verified-email skill to implement the Credential Manager request flow for retrieving a verified email address in your Android application.

Frequently Asked Questions about verified-email

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

FAQPage Schema
How do I implement OTP-less email verification on Android?

OTP-less email verification on Android uses the Credential Manager API and OpenID4VP standards to retrieve cryptographically signed digital credentials, replacing manual verification codes with trusted provider data.

What is the OpenID4VP standard for passwordless authentication?

OpenID4VP is a standard used to facilitate secure, passwordless authentication flows by requesting cryptographically signed digital credentials from trusted providers, allowing instant verification of user identity attributes.

How do I validate SD-JWT tokens from the Android Credential Manager?

Validating SD-JWT tokens requires server-side verification of the token's cryptographic signature and issuer authenticity, alongside strict nonce integrity checks to prevent replay attacks.

Does the Android Credential Manager support passkeys and verified email retrieval?

Yes, the Android Credential Manager supports retrieving verified email addresses and passkeys by integrating with the credentials and credentials-play-services-auth libraries to request user identity attributes.

Why do I need server-side validation for SD-JWT responses?

Server-side validation for SD-JWT responses is required to verify issuer authenticity and enforce nonce integrity, which prevents replay attacks during the passwordless authentication flow.

Best way to prevent replay attacks during Android passwordless authentication?

The best way to prevent replay attacks during Android passwordless authentication is to implement server-side validation of SD-JWT responses with strict nonce integrity checks.