enterprise-three-factor-auth

Verify company name, unified social credit code, and legal representative against official registry data.

23|4|Updated May 7, 2026
One-click install
npx skills add https://github.com/qq5855144/GitHubM --skill enterprise-three-factor-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise-three-factor-auth
Source: https://github.com/qq5855144/GitHubM/tree/main/.skills/enterprise-three-factor-auth
Command: npx skills add https://github.com/qq5855144/GitHubM --skill enterprise-three-factor-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of checking whether a company name, unified social credit code, and legal representative are consistent with official business registration data.

Core Features & Use Cases

  • Three-factor verification: Validates company identity by comparing the submitted enterprise name, credit code, and legal person name.
  • Mismatch diagnostics: Returns a specific result code so you can see whether the company name, credit code, or legal representative is inconsistent.
  • Compliance and onboarding: Useful for vendor review, enterprise account setup, KYC-style business checks, and工商信息核验.

Quick Start

Use the enterprise-three-factor-auth skill to verify the company name, credit code, and legal representative for the business record I provide.

Frequently Asked Questions about enterprise-three-factor-auth

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

FAQPage Schema
How do I verify a company name, unified social credit code, and legal representative against official business registry data?

Enterprise three-factor verification validates company identity by comparing the submitted enterprise name, credit code, and legal person name against official business registration data. It applies to enterprise identity verification, compliance checks, onboarding review, and company information validation workflows.

What does a mismatch diagnostic return when business registry verification fails?

Business registry verification returns a specific result code during a mismatch, indicating exactly whether the company name, credit code, or legal representative is inconsistent with official records. This explicit handling of mismatch codes helps diagnose precise enterprise identity validation failures.

When do I need to perform enterprise identity verification for vendor review or onboarding?

Enterprise identity verification is needed for compliance checks, vendor review, enterprise account setup, and KYC-style business checks. It confirms that a company's official business registry data matches the submitted records before onboarding approval.

Can I use business registry verification for KYC-style business checks and compliance workflows?

Yes, business registry verification supports KYC-style business checks and compliance workflows by validating the enterprise name, credit code, and legal person name. It requires precise parameter input to successfully decode API-based results for onboarding review.

Why does company information validation require precise parameter input for API-based result decoding?

Company information validation requires precise parameter input because the API-based result decoding explicitly handles mismatch codes and request failures. Accurate entry of the enterprise name, credit code, and legal representative ensures correct business registry data comparison.

How to handle request failures and mismatch codes during enterprise three-factor authentication?

Handle request failures and mismatch codes during enterprise three-factor authentication by reviewing the specific result code returned. This code explicitly identifies whether the company name, credit code, or legal representative is inconsistent with official business registry data.