verified-email

Name: verified-email
Availability: InStock
Author: mymx2

Implements cryptographically verified email retrieval in Android apps via Credential Manager API.

4|Updated Jun 10, 2026

Search Tags:#authentication #android #passkeys #sd-jwt #openid4vp #verified email #credential manager

Ready to run

npx skills add https://github.com/mymx2/foreman --skill verified-email-mymx2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verified-email
Source: https://github.com/mymx2/foreman/tree/main/.qoder/skills.collected/skills/verified-email
Command: npx skills add https://github.com/mymx2/foreman --skill verified-email-mymx2

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 problem of high-friction sign-up and authentication processes by replacing traditional, manual email verification methods like OTPs with cryptographically verified credentials.

Core Features & Use Cases

Credential Manager Integration: Provides a standardized workflow for requesting and parsing verified email claims from the Android Credential Manager API.
Enhanced Security: Leverages OpenID4VP and SD-JWT standards to ensure data authenticity and presenter identity, reducing the risk of spoofing.
Use Case: Streamline user onboarding by verifying email ownership during account creation or recovery without requiring users to check their inbox for verification codes.

Quick Start

Use the verified-email skill to implement the Credential Manager request flow for retrieving a user's 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?▼

To implement OTP-less email verification on Android, use the Credential Manager API and OpenID4VP standards to request cryptographically verified email claims. This eliminates manual verification codes by securely retrieving verified credentials directly from the user's device.

What are the requirements for Android Credential Manager passkey authentication?▼

Android Credential Manager passkey authentication requires Android SDK 28 or higher and Google Play services version 25.49.x. You also need the androidx.credentials dependencies to perform secure credential requests and server-side validation.

How does SD-JWT verification work with OpenID4VP?▼

SD-JWT verification with OpenID4VP works by selectively disclosing JSON claims to ensure data authenticity and presenter identity. This cryptographic standard reduces spoofing risks by validating the verified email credential directly during the authentication flow.

Can I use Credential Manager for account recovery flows without OTP codes?▼

Yes, you can use Credential Manager for account recovery flows without OTP codes by requesting verified email claims cryptographically. This streamlines user onboarding and recovery by verifying email ownership securely without requiring users to check their inbox.

Does verified email retrieval work with older Android SDK versions?▼

Verified email retrieval does not work with older Android SDK versions below 28. The cryptographic credential requests and server-side validation processes explicitly require Android SDK 28 or higher along with Google Play services 25.49.x.

What is the best way to secure user authentication on Android without manual verification codes?▼

The best way to secure user authentication without manual verification codes is leveraging Credential Manager API with OpenID4VP and SD-JWT standards. This approach provides cryptographically verified email retrieval, ensuring presenter identity and eliminating reliance on manual OTP verification.