Choose a Twilio Sender Type with Codex
Compare sender requirements before implementation using destination, two-way reply needs, throughput, and onboarding evidence.
中文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-numbers-senders and paste the example inputs. Use the installed package with its related skills and references.
Example task
Ask $twilio-numbers-senders to plan a fictional appointment service that needs two-way replies and runs in two regions. Provide no approved sender inventory. Return a requirements table and a list of facts to verify for each region.Expected result
The plan carries the two-way requirement into both rows and treats sender availability and local onboarding as unknown until checked. It proposes no number purchases.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
What should I decide before buying a sender?
Confirm the destination, expected message pattern, need for replies, and current sender availability or onboarding requirement for that use case.