verified-email
Provides a complete workflow for implementing verified email retrieval
Install / Use
npx skills add android/skills --skill verified-emailInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of verified-email
verified-email scores 92/100 on our quality scale, 820th of 2,790 Automation skills we index (top 30%).
Its SKILL.md is 20 KB long, well organised into 26 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 7,514 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so verified-email is actively maintained.
- Our last check on 2026-10-05 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
verified-email compared with similar skills
All 4 of these similar skills score higher than verified-email; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| verified-email (this skill)by android | 92 | 7.5k | 54d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
Frequently asked questions
- How do I install verified-email?
- Run
npx skills add android/skills --skill verified-email. The install tabs above show the steps for each supported agent. - Which AI agents does verified-email work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is verified-email safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is verified-email still maintained?
- The repository was last updated about 2 months ago, so verified-email is actively maintained.
Skill content
View source on GitHubname: verified-email description: Provides a complete workflow for implementing verified email retrieval on Android Credential Manager API. Use this skill to integrate a secure, OTP-less email verification flow into an Android app. This skill solves the problem of high-friction sign-up processes by leveraging cryptographically verified credentials from trusted providers like Google. license: Complete terms in LICENSE.txt metadata: author: Google LLC last-updated: '2026-09-16' keywords:
- implementation
- Android
- Credential Manager
- Digital Credentials
- Verified Email
- OpenID4VP
- SD-JWT
- OTP-less
- authentication
- passkeys
- CredMan
- identity.
Fundamentals
- Overview of Digital Credentials: Learn about cryptographically verifiable documents and the role of Credential Manager.
- Glossary : Definitions for
dcql_query,UserInfoCredential, andGetDigitalCredentialOption.
Standards & Examples
- OpenID4VP Standard: The specification used to create digital credentials requests.
- Digital Credentials Demo: Example requests and cross-platform testing tool.
- W3C Verifiable Credentials: The data model for cryptographically secured claims.
- SD-JWT: Selective Disclosure JSON Web Token format used for responses.
- mdoc: ISO/IEC 18013-5 standard for mobile documents.
Requirements
- SDK Version: Minimum SDK 28 (Android 9) is required.
- GMS Version: Google Play services version 25.49.x or higher.
Use Cases
Email verification is applicable for the following use cases:
- Account Creation/Sign-up: Remove friction by skipping manual email verification.
- Account Recovery: Securely verify email ownership during recovery flows.
- Re-authentication: Versatile verification for high-risk actions, independent of the initial sign-in method.
Limitations & Nuances
- Workspace Accounts: Google does not issue verifiable credentials for Google Workspace Accounts.
- Freshness: For non-@gmail.com addresses, Google verifies the email at account creation but there is no freshness claim; implement an additional challenge like an OTP.
Scope & Pre-requisites
Crucial : This skill focuses exclusively on the Android client-side integration . It does not implement the app's server-side cryptographic validation logic. Server-side validation of the returned credential is required for security and must be implemented in your backend.
Codebase exploration for Use Cases
Get started with the following queries in project source code to find relevant screens with different use cases to implement verified email:
SignUpScreen"Email address""Recover Account""Account Recovery""Forgot password?""Delete Account"
Identifying Integration Points
To implement this feature effectively, you must first locate the relevant flows in your codebase. To initiate, start with the following strategies to cater to different use cases using verified email:
1. Search for Navigation Routes
If your app uses Navigation, search for routes or destinations related to authentication:
Look for:
- Keywords :
signup,registration,create_account,forgot_password,recovery,verify_email. - Code Pattern : Search for
NavHostorcomposabledestinations using these strings.
2. Locate Authentication ViewModels
Find the business logic handling user attributes and account creation, account recovery:
- Keywords :
SignUpViewModel,AuthViewModel,RegistrationRepository. - Code Pattern : Look for methods like
onCreateAccount,onRecoverAccount, orvalidateEmail.
3. Find instances of reauthentication for sensitive actions
For reauthentication use cases, find areas where users perform sensitive actions:
- Keywords :
ChangePassword,UpdatePayment,DeleteAccount,UpdateDetails,EditUserDetails
Important pointers for Implementation
- Construct a Digital Credential Request and present it to the user.
- Make sure to follow the request JSON structure as mentioned in documentation.
- While presenting the request to the user, check if result credential is DigitalCredential and credential.credentialJson as responseJsonString
- Parse the response from the client.
- Offer a passkey creation option if one is not already present.
- Assume a local
SdJwtParserto parse raw SD-JWT and return aJSONObject. - Use a
VerifiedUserInfodata class to store the parsed name and email. - Leave a TODO for developers to handle the app's server-side validation and parsing.
- Direct users to the home screen after API call success and show a snackbar with user details for reference purpose only.
Overview
This guide describes how to implement verified email retrieval using the Digital Credentials Verifier API through an OpenID for Verifiable Presentations (OpenID4VP) request.
Add dependencies
In your app's build.gradle file, add the following dependencies for Credential
Manager:
Kotlin
dependencies {
implementation("androidx.credentials:credentials:1.7.0-alpha03")
implementation("androidx.credentials:credentials-play-services-auth:1.7.0-alpha03")
}
Groovy
dependencies {
implementation "androidx.credentials:credentials:1.7.0-alpha03"
implementation "androidx.credentials:credentials-play-services-auth:1.7.0-alpha03"
}
Initialize Credential Manager
Use your app or activity context to create a CredentialManager object.
// Use your app or activity context to instantiate a client instance of
// CredentialManager.
private val credentialManager = CredentialManager.create(context)
Construct the Digital Credential request
To request a verified email, construct a GetCredentialRequest
containing a GetDigitalCredentialOption. This option requires a
requestJson string formatted as an OpenID for Verifiable Presentations
(OpenID4VP) request.
The OpenID4VP request JSON must follow a specific structure. The current
providers support a JSON structure with an outer "digital": {"requests": [...]} wrapper.
val nonce = generateSecureRandomNonce()
// This request follows the OpenID4VP spec
val openId4vpRequest = """
{
"requests": [
{
"protocol": "openid4vp-v1-unsigned",
"data": {
"response_type": "vp_token",
"response_mode": "dc_api",
"nonce": "$nonce",
"dcql_query": {
"credentials": [
{
"id": "user_info_query",
"format": "dc+sd-jwt",
"meta": {
"vct_values": ["UserInfoCredential"]
},
"claims": [
{"path": ["email"]},
{"path": ["name"]},
{"path": ["given_name"]},
{"path": ["family_name"]},
{"path": ["picture"]},
{"path": ["hd"]},
{"path": ["email_verified"]}
]
}
]
}
}
}
]
}
"""
val getDigitalCredentialOption = GetDigitalCredentialOption(requestJson = openId4vpRequest)
val request = GetCredentialRequest(listOf(getDigitalCredentialOption))
The request contains the following key information:
-
DCQL query : The
dcql_queryspecifies the credential type and the claims being requested (email_verified). You can request other claims to determine the level of verification. A few possible claims are as follows:email_verified: In the response, this is a Boolean that indicates whether the email is verified.hd(hosted domain): In the response, this is empty.
[!NOTE] Note: If
email_verifiedistrueandhdis empty in the response, it implies that the account is an authorized Google Account. Google does not issue verifiable credentials for Google Workspace Accounts. However, thehdfield is present in verifiable credentials issued for non-workspace accounts. You are encouraged to implement handling this field to future-proof your app. If the email is non-@gmail.com, Google verified this email when the Google Account was created, but there is no freshness claim. Therefore, for non-Google emails, you should consider an additional challenge, such as an OTP, to verify the user. To understand the schema of the credential and the specific rules for validating fields likeemail_verified, refer to the Google Identity guides. -
nonce: A unique, cryptographically secure random value is generated for each request. This is critical for security, as it prevents replay attacks.
-
UserInfoCredential: This value implies a specific type of digital credential that contains user attributes. Including this in the request is pivotal to distinguish the email verification use case.
Next, wrap the openId4vpRequest JSON in a GetDigitalCredentialOption, create
a GetCredentialRequest, and call getCredential().
[!NOTE] Note: The
hdandemail_verifiedfields are hidden from users in Credential Manager's built-in UI. You cannot make a request with only these hidden fields- in case of such requests, the response is theGetCredentialCancellationException.
Present the request to the user
Present the user with the request, using the Credential Manager built-in UI.
coroutineScope {
try {
// Requesting Digital Credential from user...
val result = credentialManager.getCredential(activity, request)
when (val credential = result.credential) {
is DigitalCredential -> {
val responseJsonString = credential.credentialJson
// Successfully received digital credential response.
// Next, parse this response and send it to your server.
// ...
}
else -> {
// handle Unexpected State() - Up to the developer
}
}
} catch (e: Exception) {
// handle exceptions - Up to the developer
}
}
[!NOTE] Note: There is no equivalent of Sign in with Google's
preferImmediatelyAvailableCredentialsfor Digital Credentials. If no verifiable credential is found (for example, no eligible account on device), the user will be shown a "No options available" or similar system screen.
Parse the response on the client
[!WARNING] Warning: From August 2026, the response JSON format has been updated to strictly match the W3C standards. It contains
dataand `protocol
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
