id-card-two-factor-auth

Validate Chinese ID card numbers against names and return identity attributes.

23|4|Updated May 7, 2026

Search Tags:#compliance #api integration #kyc #identity verification #id verification #real-name authentication

Ready to run

npx skills add https://github.com/qq5855144/GitHubM --skill id-card-two-factor-auth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: id-card-two-factor-auth
Source: https://github.com/qq5855144/GitHubM/tree/main/.skills/id-card-two-factor-auth
Command: npx skills add https://github.com/qq5855144/GitHubM --skill id-card-two-factor-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the manual burden of checking whether an ID card number and name belong to the same person, making identity verification faster and more reliable for applications that require real-name checks.

Core Features & Use Cases

Two-factor identity matching: Confirms whether the provided name and ID card number match.
Identity details return: Extracts sex, birthday, and registered region information for downstream workflows.
Operational safeguards: Handles common API outcomes such as invalid formats, duplicate requests, unsupported regions, and rate limits.
Use case: A signup flow can call this Skill to validate a user's legal identity before granting access to regulated features.

Quick Start

Use this skill to verify whether the provided name and ID card number match and return the parsed identity details.

Frequently Asked Questions about id-card-two-factor-auth

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

FAQPage Schema

How do I verify a Chinese ID card number and real name match for KYC compliance?▼

Identity verification for KYC compliance checks whether a Chinese ID card number and real name belong to the same person. This Skill validates the match and returns identity attributes like sex, birthday, and registered region for downstream workflows.

What identity attributes are returned during real-name authentication?▼

Real-name authentication returns parsed identity details including sex, birthday, and registered region information. These attributes are extracted after confirming the provided name and ID card number match, enabling deterministic identity lookup for backend verification workflows.

How do I integrate ID verification into a signup flow using API calls?▼

API integration for ID verification requires URL-encoded name input and platform-managed authorization. A signup flow can call this Skill to validate a user's legal identity before granting access to regulated features by parsing response match codes and error states.

Does two-factor identity matching handle invalid formats and rate limits?▼

Two-factor identity matching includes operational safeguards that handle common API outcomes such as invalid formats, duplicate requests, unsupported regions, and rate limits. This ensures reliable compliance screening without manual intervention for standard API errors.

When do I need real-name authentication for backend verification workflows?▼

Real-name authentication is needed for backend verification workflows that require deterministic identity lookup, such as KYC checks and compliance screening. It confirms whether provided name and ID card number match before granting access to regulated features.

Why does my identity verification API return an unsupported region error?▼

Identity verification API responses include error states for unsupported regions, invalid formats, and duplicate requests. Parsing these match codes and error states helps identify whether the input ID card number falls outside supported regions or contains formatting issues.