Plan Signup Verification with Twilio and Codex
Choose where basic validation and user verification belong in a signup flow and define how the app should handle an unconfirmed attempt.
中文Setup for Codex (Twilio Developer Kit)
Use Codex in a scratch workspace and keep the exercise on fictional data. For a live sandbox, confirm the latest provider requirements and the permissions for the selected Twilio product.
- Open /plugins in Codex and install Twilio Developer Kit. The pinned source below includes the official Codex setup instructions.
- Invoke $twilio-identity-verification-advisor in a practice project and supply the local fixture below. Keep companion skills and references in the plugin.
Example task
Give $twilio-identity-verification-advisor a fictional book-club signup with one channel and no payment. Ask for a state diagram covering format invalid, pending verification, and verified, then test one fixture for each.Expected result
Invalid input stops before the verifier, pending does not enable the verified feature, and verified advances the workflow. The plan identifies when additional risk signals would need evidence.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
When should the flow include both Lookup and Verify?
Decide whether the app needs an input check, proof of control, or both. Record the purpose of each step and test the outcomes independently.