Plan a Twilio HIPAA Readiness Review in Codex
Build a technical readiness checklist from a fictional healthcare workflow and mark where agreement or service eligibility evidence is missing.
中文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-security-compliance-hipaa in a practice project and supply the local fixture below. Keep companion skills and references in the plugin.
Example task
Use $twilio-security-compliance-hipaa on a synthetic appointment system description with application, logs, and messaging. Label protected data as a placeholder. Provide no real patient details or account, and ask for the Twilio eligibility and agreement checks to verify before launch.Expected result
The checklist treats both account evidence and eligible product configuration as unverified, and flags logs for data minimization and review. It makes no compliance determination.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Does a signed agreement complete the technical review?
Check the current Twilio eligible-services list and your architecture, data handling, and agreement with the appropriate reviewers. The example is a readiness inventory.