ekx-twiliolisted

SMS, WhatsApp, voice and OTP verification with Twilio — the official skills and MCP server, how it compares to the Meta Graph API we already use for WhatsApp, and the compliance work Colombian and US messaging actually requires. Use when a product needs SMS, phone verification, voice, or a second WhatsApp path. NOT YET IN PRODUCTION anywhere — read the "before you adopt" section first.
Ekinoxis-evm/claude-skills · ★ 0 · AI & Automation · score 60

Install: claude install-skill Ekinoxis-evm/claude-skills

# Twilio > ⚠️ **Not used in any Ekinoxis project.** Audited every `package.json`, `.env.example` and > source file on 2026-08-28: **zero integration.** This skill exists so that adopting Twilio > is a decision with the trade-offs written down, not a default. ## What we do today instead | Need | What we actually run | |---|---| | WhatsApp | **Meta Graph API** directly — [`ekx-meta-ads`](../ekx-meta-ads/SKILL.md), plus a WhatsApp sales agent running on n8n | | Transactional email | **Resend** — [`ekx-resend`](../ekx-resend/SKILL.md), 4 projects | | Auth / identity | **Privy** (email OTP, social, wallet) — [`ekx-privy`](../ekx-privy/SKILL.md), 5 projects. **Supabase Auth** email OTP elsewhere | | SMS | **nothing** | | Voice | **nothing** | **SMS and voice are the genuine gaps.** Everything else Twilio sells, we already have a working answer for. ## Before you adopt Ask in this order: 1. **Is it really SMS you need, or just a one-time code?** Supabase Auth and Privy both do email OTP today, in production, at no extra vendor. Our commerce stack uses passwordless email OTP and has never needed SMS. 2. **Is it WhatsApp?** We already send WhatsApp through Meta's Graph API. Twilio would be a *second* path to the same channel — more surface, another bill, another set of template approvals. 3. **Is it voice, or SMS to a Colombian mobile?** Then yes — Twilio, or a local aggregator. Nothing we own covers that. If the answer is (3), continue. Otherwise stop. ## Offi