email-validator Eval-Bericht.

Validierungsplan

Was der Agent als Nächstes tun sollte

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Nicht verwenden, wenn

Bedingungen für eine andere Skill

• Teams, die ein vom Anbieter unterstütztes SLA benötigen
• production agents without a repository review
• The API map file is circular: it only says 'See sandbase_describe_tool for details' for every tool, so SKILL.md does not independently document inputs, outputs, or limitations.
• No explicit security guidance for handling untrusted email data or API responses as potential prompt-injection content.
• No setup or prerequisites are documented, such as SandBase gateway availability, authentication assumptions, rate limits, or PII handling expectations.
• No examples or expected output format are provided, which may lead to inconsistent synthesis of results.