银行卡三要素核验 - 聚合数据
v1.0.0银行卡三要素核验。验证银行卡号、姓名、身份证号三要素是否一致。使用场景:用户说"验证银行卡"、"核验银行卡三要素"、"银行卡实名认证"、"检查银行卡号和身份证是否匹配"、"银行卡三元素检测"等。通过聚合数据(juhe.cn)API实时核验,支持单次查询和批量核验。
⭐ 0· 93·0 current·0 all-time
byjuhe-skills@juhemcp
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the implementation: the script calls the juhe.cn verifybankcard3 API and the skill requires python3 and JUHE_BANKCARD3_KEY — all are appropriate and expected for this purpose.
Instruction Scope
SKILL.md and the script instruct the agent to extract bank card number, real name, and ID number from user input and call the juhe API. This is within the declared scope, but it explicitly handles very sensitive PII. Additionally, the API URL in the script uses http (cleartext) which can expose API keys and PII in transit or in logs — consider using a TLS/HTTPS endpoint if available and confirm the provider's recommended endpoint.
Install Mechanism
No install spec — instruction-only with a small Python script. Required binary is only python3; no downloads or third-party package installs are performed by the skill itself. Low installation risk.
Credentials
Only JUHE_BANKCARD3_KEY is required as the primary credential, which is proportionate for calling juhe.cn. The script reads the key from env, .env, or CLI arg — behavior matches declared env requirement.
Persistence & Privilege
always is false and the skill does not request persistent elevated privileges or modify other skills. Autonomous invocation is allowed (platform default) but not combined with broad credential access.
Assessment
This skill does what it says: it collects bank card number, name, and ID number and sends them to juhe.cn for verification. Before installing or using it, consider: (1) Privacy/consent — you must have the user's explicit consent to submit their PII to a third party and comply with local regulations. (2) Transport security — the script uses an http API URL; that can expose API keys and PII in transit and to intermediaries or logs. Prefer an HTTPS endpoint (check juhe.cn docs) or a provider that guarantees TLS. (3) API key handling — store JUHE_BANKCARD3_KEY in a restricted environment variable or secret store; avoid committing .env files to repos. (4) Batch data — if you use CSV batch mode, ensure files with PII are stored and deleted securely. (5) Rate limits and billing — the provider may limit calls or charge for usage; handle error codes accordingly. If you need the skill to never transmit raw identifiers, request a design change (e.g., hashed/local-only checks) or confirm the provider's encryption and logging policies. If you want, I can draft a safer configuration checklist or show how to modify the script to use HTTPS and avoid sending the key in the URL query string.Like a lobster shell, security has layers — review code before you run it.
latestvk9727gx4jtxqjqy1n1njf8j1v583nq2n
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
💳 Clawdis
Binspython3
EnvJUHE_BANKCARD3_KEY
Primary envJUHE_BANKCARD3_KEY
