Design Transactional Alerts with Twilio and Codex
Plan delivery channels and acknowledgements for transactional alerts before connecting a Twilio account.
中文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-notifications-alerts-advisor and paste the example inputs. Use the installed package with its related skills and references.
Example task
Give $twilio-notifications-alerts-advisor two fictional event classes, appointment reminder in one day and an urgent service alert that must be acknowledged. Ask it to model pending, acknowledged, and escalation in a local queue.Expected result
The plan distinguishes reminder delivery from acknowledgement. An acknowledgement suppresses escalation and a simulated timeout triggers a fallback record.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Does a delivery receipt mean the person acknowledged the alert?
A receipt gives transport evidence. Treat user acknowledgement as a separate, explicitly recorded event in the application.