email-validity-check@1.0.2
VERIFIED· install onlyPublisher claims: "Verify email validity and format, cut email bounce‑rates and clean contact lists for exporters, recruiters and B2B sales teams. Trigger: email address validation, reduce email bounce rate, email‑list scrubbing, CRM data cleansing, cold outreach optimization" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-08 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
- **API Key**: Stored in `~/.upkuajing/.env` file as `UPKUAJING_API_KEY`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.First check if the `~/.upkuajing/.env` file has UPKUAJING_API_KEY;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# 读取现有的 .env 文件Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# 保存到 .env 文件Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.1. User has one: User provides it (manually add to ~/.upkuajing/.env file)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- **API key invalid/non-existent**: Check `UPKUAJING_API_KEY` in `~/.upkuajing/.env` fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# 检查是否已存在 .env 文件和 API keyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."message": f"API密钥申请成功,但保存到 .env 文件失败:{str(e)}。\n请手动设置环境变量 {API_KEY_ENV}。",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.UPKUAJING_ENV_FILE = UPKUAJING_DIR / '.env'Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.获取API密钥,优先从环境变量,其次从 ~/.upkuajing/.env 文件。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# 如果环境变量没有,尝试从 ~/.upkuajing/.env 读取Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.从 ~/.upkuajing/.env 文件加载环境变量。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.