Test a Twilio Verify OTP Flow in Codex
Use a local Verify adapter fixture to check how a signup form handles approval, expiry, and repeat attempts.
中文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-verify-send-otp and paste the example inputs. Use the installed package with its related skills and references.
Example task
Model a sandbox signup with a stubbed Verify service. Use three fixed adapter results, pending, approved, and expired. Use the same approved result twice and record when the demo account changes verification state.Expected result
Pending leaves the gate closed, approved verifies eligibility once, and expired offers a new test attempt. The second approved callback does not trigger another account update.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Does this exercise need a real phone number or message?
The fixture uses state labels and a fake account. A live delivery test needs the appropriate Twilio service and a test recipient you control.