Plan Twilio Email Deliverability Checks with Codex
Prioritize email deliverability steps using a fictional domain and evidence from a mock bounce and authentication report.
中文Setup for Codex (Twilio Developer Kit)
Use Codex in a scratch workspace. The exercise takes local mock data or a written scenario. Check provider prerequisites before running it against a test account.
- In Codex, open /plugins and install Twilio Developer Kit. To reproduce the exact revision, use the pinned Twilio source linked below and its Codex instructions in the repository README.
- Open the practice project, invoke $twilio-email-deliverability-advisor and paste the example inputs. Use the installed package with its related skills and references.
Example task
Give $twilio-email-deliverability-advisor fixture rows reporting one hard bounce and one authentication status unknown. Ask for a checks list tied to each signal, plus a test of your own suppression logic.Expected result
The hard bounce is marked for suppression review. The unknown status calls for verification of domain authentication and yields no assumed DNS result.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Can Codex conclude deliverability from a single sample message?
One sample only exposes a small part of the send path. Compare provider events, authentication results, and a controlled test batch before drawing broader conclusions.