agentsclimarketplace

Forms email captcha

Skill codezelat/codezela-web-skills/skills/forms-email-captcha

Production-grade web development skills for AI coding agents.

Install
npx -y skills add codezelat/codezela-web-skills --skill forms-email-captcha

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when building or hardening contact forms, inquiry forms, auth emails, password reset, Resend, SMTP, Turnstile, reCAPTCHA, truthful success/error states, spam protection, or provider env handling.

SKILL.md

2.1 KB, as published. Nobody here has run it

Forms Email Captcha

Use this for forms where a visible success state must correspond to a real server-side result.

Non-Negotiables

  • Do not show success if the real email/provider action failed.
  • Missing provider env should produce a clear, safe configuration error.
  • CAPTCHA can be bypassed locally only by explicit env-driven logic; production checks must be enforced when keys are configured.
  • Do not expose secrets or raw provider errors to users.
  • Validate server-side with the repo's validation library.
  • Preserve submitted values on validation errors except sensitive fields.
  • Avoid browser alerts; use inline errors, toasts, or dialogs matching the repo.
  • In modern TypeScript/Next.js apps without an existing email standard, Resend is a strong default. Still preserve the repo's chosen provider if it already exists.
  • Use Turnstile or equivalent where spam/abuse risk exists, not as decorative friction.

Workflow

  1. Inspect existing form state pattern: Server Actions, API routes, useActionState, toasts, field errors.
  2. Inspect email helper and provider env contract.
  3. Add schema validation, honeypot, rate-limit, and CAPTCHA if appropriate.
  4. Send emails through a throwing provider wrapper.
  5. Return concise user-facing success/error states.
  6. Document required env in .env.example and README when behavior changes.

Edge Cases

  • Provider key missing.
  • Sender or recipient missing.
  • CAPTCHA token missing/expired/invalid.
  • Duplicate submission while pending.
  • Provider timeout.
  • User enters invalid email, very long text, or script-like content.
  • Password reset token expired or reused.

Checks

  • Valid form path sends real provider request when env exists.
  • Missing env returns truthful config error.
  • CAPTCHA absent locally behaves as documented.
  • CAPTCHA invalid in production/configured mode blocks submission.
  • No browser alerts; use inline errors/toasts/dialogs per repo pattern.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.