.claude/skills/looot-email-verificationRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Verify an email address. Use when the user says things like "is [email protected] a real email", "verify this list of emails before I send" or "check if this address will bounce". Runs through looot, billed per call.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/looot-email-verificationRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/looot-email-verificationRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/looot-email-verificationRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @walidboulanouar/looot-email-verificationclawhub inspect @walidboulanouar/looot-email-verification --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:976a17911cc57f9a2da9207a853110327ba37c326628ee413f8898965f0ec30eskill-card.mdSKILL.mdVersion 1.0.0 — Initial release - Verify one or more email addresses through looot providers, starting with the cheapest suitable endpoint. - Return deliverability results, catch-all status, provider details, confidence scores, and typo suggestions when available. - Require user approval after showing the endpoint and price; report batch totals and stop after two failures. - Group results as deliverable, risky, or undeliverable, keeping catch-all addresses separate.