twilio-verify-send-otp — Claude Code skill for Twilio OTP
twilio-verify-send-otp is a Claude Code skill that adds Twilio Verify flows for sending one-time codes and checking submitted OTPs, for phone or email confirmation and two-factor authentication.
MIT 191 installs ★ 42 updated 2026-10-22
npx skills add twilio/ai --skill twilio-verify-send-otp -a claude-codeWhat twilio-verify-send-otp does
The skill walks through the Verify flow: create a service, send a code, then check the submitted value. Delivery can use SMS, voice, email, or WhatsApp. When a device supports it, an SMS verification can be upgraded to RCS automatically. TOTP for authenticator apps uses the separate Verify Factors API.
You’ll need a Twilio account, the TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, and VERIFY_SERVICE_SID environment variables, plus the twilio SDK for Python or Node.js. Create the Verify Service once and reuse its SID. WhatsApp requires a registered production sender, so that channel depends on having one set up. You can enable SMS as a fallback when WhatsApp delivery fails.
What it helps with
- send a one-time code to a phone or email address
- check an OTP entered by a user
- add code delivery by voice call
- fall back to SMS when WhatsApp delivery fails
- set up TOTP with the Verify Factors API
Example prompts for the agent
- Add a Twilio Verify flow that sends an OTP by SMS and checks the submitted code.
- Set up email confirmation with Twilio Verify.
- Configure WhatsApp OTP delivery with SMS fallback if the message fails.
How to install twilio-verify-send-otp
1Skills CLI (Vercel)
npx skills add twilio/ai --skill twilio-verify-send-otp -a claude-code2Manually: put the files in place
~/.claude/skills/twilio-verify-send-otp/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/twilio-verify-send-otp/
1Skills CLI (Vercel)
npx skills add twilio/ai --skill twilio-verify-send-otp -a codex2Manually: put the files in place
.agents/skills/twilio-verify-send-otp/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add twilio/ai --skill twilio-verify-send-otp -a cursor2Manually: put the files in place
.cursor/skills/twilio-verify-send-otp/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install twilio/ai skills/twilio/twilio-verify-send-otp2Manually: put the files in place
.github/skills/twilio-verify-send-otp/SKILL.md1Skills CLI (Vercel)
npx skills add twilio/ai --skill twilio-verify-send-otp -a gemini-cli2Platform CLI
gemini skills install https://github.com/twilio/ai --path skills/twilio/twilio-verify-send-otpManually: put the files in place
.devin/skills/twilio-verify-send-otp/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add twilio/ai --skill twilio-verify-send-otp -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about twilio-verify-send-otp
How do I install twilio-verify-send-otp in Claude Code?
Run npx skills add twilio/ai --skill twilio-verify-send-otp -a claude-code. The skill file is at ~/.claude/skills/twilio-verify-send-otp/SKILL.md.
What does twilio-verify-send-otp do?
It guides you through creating a Verify Service, sending a one-time code through a supported channel, and checking the submitted code. It also covers WhatsApp delivery with SMS fallback.
What do I need to use WhatsApp for OTP delivery?
You need a registered production WhatsApp sender. Enable SMS as well to use it as a fallback if WhatsApp delivery fails.
Source text
SKILL.md · MIT
---
name: twilio-verify-send-otp
description: >
Send and verify one-time passcodes (OTPs) via Twilio Verify over SMS
(auto-upgraded to RCS where supported), voice, email, or WhatsApp. Covers
creating a Verify Service, sending tokens,
checking submitted codes, automatic WhatsApp-to-SMS fallback, and service
configuration. TOTP is supported via the Factors API (a separate family from
channel-based OTP). Use this skill to add phone or email verification or
two-factor authentication to any application.
---
## Overview
Use **Twilio Verify** to manage the full OTP lifecycle: code generation, delivery, expiry, rate limiting, and Fraud Guard protection. Use the **Programmable Messaging API** to build your own OTP message infrastructure and access features such as SMS Pumping Protection.
| | Twilio Verify | Programmable Messaging API |
|---|---|---|
| Code generation + expiry | Built-in (10min default, configurable). Also supports custom codes. | Build yourself |
| Rate limiting | Built-in (per-phone, per-service) | Build yourself |
| Fraud protection | Fraud Guard (geo-permissions, rate anomaly) | SMS Pumping Protection |
| A2P registration | Exempt — no 10DLC needed | Required — must register campaign |
| Multi-channel | One API, change `channel` param (SMS/Voice/Email/WhatsApp) | Separate integration per channel |
| Cost | [Per confirmed verification + channel fee](https://www.twilio.com/en-us/verify/pricing) | Per-message pricing + build cost |
| Delivery confirmation | Yes — via List Attempts or Events API | Yes (via StatusCallback) |
**When Programmable Messaging is justified:** You need full control over message content, custom delivery logic, or SMS Pumping Protection features. For standard OTP/2FA flows, use Verify.
Verify supports SMS, voice, email, and WhatsApp — only the `channel` parameter changes per delivery method. RCS is not a `channel` value: Verify automatically upgrades an `sms` verification to RCS where the device supports it and falls back to SMS. TOTP (authenticator apps) is supported via the Verify Factors API, a separate implementation from channel-based OTP.
---
## Prerequisites
- Twilio account (free trial works for testing)
— New to Twilio? See `twilio-account-setup`
— Verify requires no separate product activation — just create a Service below
- Environment variables:
- `TWILIO_ACCOUNT_SID`
- `TWILIO_AUTH_TOKEN`
- `VERIFY_SERVICE_SID` (created in Quickstart step 1)
— See `twilio-iam-auth-setup` for credential setup and best practices
- SDK: `pip install twilio` / `npm install twilio`
- For WhatsApp channel only: a registered production WhatsApp sender — see `twilio-whatsapp-manage-senders`
---
## Quickstart
**Step 1 — Create a Verify Service (one-time)**
**Python**
```python
import os
from twilio.rest import Client
client = Client(os.environ["TWILIO_ACCOUNT_SID"], os.environ["TWILIO_AUTH_TOKEN"])
service = client.verify.v2.services.create(
friendly_name="My App Verification"
)
print(service.sid) # VAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx — save as VERIFY_SERVICE_SID
```
**Node.js**
```node
const twilio = require("twilio");
const client = twilio(process.env.TWILIO_ACCOUNT_SID, process.env.TWILIO_AUTH_TOKEN);
const service = await client.verify.v2.services.create({
friendlyName: "My App Verification",
});
console.log(service.sid); // VAxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
```
Store the Service SID — reuse it for all verifications, do not recreate it each time.
**Step 2 — Send a verification token**
**Python**
```python
verification = client.verify.v2 \
.services(os.environ["VERIFY_SERVICE_SID"]) \
.verifications \
.create(to="+15558675310", channel="sms")
print(verification.status) # pending
```
**Node.js**
```node
const verification = await client.verify.v2
.services(process.env.VERIFY_SERVICE_SID)
.verifications.create({ to: "+15558675310", channel: "sms" });
console.log(verification.status); // pending
```
**Step 3 — Check the submitted code**
**Python**
```python
check = client.verify.v2 \
.services(os.environ["VERIFY_SERVICE_SID"]) \
.verification_checks \
.create(to="+15558675310", code="123456")
if check.status == "approved":
print("Verified!")
else:
print("Invalid or expired code")
```
**Node.js**
```node
const check = await client.verify.v2
.services(process.env.VERIFY_SERVICE_SID)
.verificationChecks.create({ to: "+15558675310", code: "123456" });
if (check.status === "approved") {
console.log("Verified!");
} else {
console.log("Invalid or expired code");
}
```
---
## Key Patterns
### Supported Channels
| Channel | `channel` value | Notes |
|---------|----------------|-------|
| SMS | `sms` | Default, widest coverage. Auto-upgrades to RCS where supported (see below) |
| Voice call | `call` | Reads code aloud |
| Email | `email` | Use email address in `to` |
| WhatsApp | `whatsapp` | Requires own WhatsApp sender (see below) |
> **TOTP (authenticator apps):** Supported via the Verify Factors API — a separate implementation from channel-based OTP. See [Verify TOTP docs](https://www.twilio.com/docs/verify/quickstarts/totp).
### WhatsApp OTP
Change `channel` to `"whatsapp"` — the send/check flow is identical to SMS.
> **Requires:** A registered production WhatsApp sender. As of March 2024, Twilio no longer provides a shared sender for Verify. See `twilio-whatsapp-manage-senders`.
**Python**
```python
verification = client.verify.v2 \
.services(os.environ["VERIFY_SERVICE_SID"]) \
.verifications \
.create(to="+15558675310", channel="whatsapp")
```
**Node.js**
```node
const verification = await client.verify.v2
.services(process.env.VERIFY_SERVICE_SID)
.verifications.create({ to: "+15558675310", channel: "whatsapp" });
```
### WhatsApp with Automatic SMS Fallback
**Python**
```python
verification = client.verify.v2 \
.services(os.environ["VERIFY_SERVICE_SID"]) \
.verifications \
.create(
to="+15558675310",
channel="whatsapp",
channel_configuration={
"whatsapp": {"enabled": True},
"sms": {"enabled": True} # falls back to SMS if WhatsApp undelivered
}
)
```
**Node.js**
```node
const verification = await client.verify.v2
.services(process.env.VERIFY_SERVICE_SID)
.verifications.create({
to: "+15558675310",
channel: "whatsapp",
channelConfiguration: {
whatsapp: { enabled: true },
sms: { enabled: true },
},
});
```
With fallback enabled, your UI can say "a verification code was sent" without specifying the channel.
### Service Configuration
**Python**
```python
service = client.verify.v2.services.create(
friendly_name="My App",
code_length=6 # 4–10 digits (default: 6)
)
```
**Node.js**
```node
const service = await client.verify.v2.services.create({
friendlyName: "My App",
codeLength: 6
});
```
### Verification Status Values
| Status | Meaning |
|--------|---------|
| `approved` | Code is correct |
| `pending` | Code is wrong or not yet submitted |
| `expired` | Code has expired (default TTL: 10 minutes) |
| `canceled` | Verification was canceled |
---
## Debugging
**Primary debugging tool:** Console > Verify > Logs (per-Service). Shows every verification attempt, delivery status, channel used, and error codes. Check here first before writing custom monitoring code.
### Common Errors
| Code | Meaning | Fix |
|------|---------|-----|
| 60200 | Invalid parameter | Check `to` format and `channel` value |
| 60202 | Max check attempts reached | Issue a new verification |
| 60203 | Max send attempts reached | Wait before retrying |
| 60212 | Service not found | Verify `VERIFY_SERVICE_SID` is correct |
| 60410 | Geo-permission not enabled | Enable country in Console |
**Built-in protections (no custom code needed):**
- Rate limiting: 5 verifications per phone per service per 10 minutes
- Max check attempts: 5 per verification (6th attempt → error 60202)
- Phone number validation: Verify checks line type before sending (if `lookup_enabled=True`)
- Fraud Guard: geo-permissions, rate anomaly detection, SMS pumping protection
**International OTP traffic warning:** International numbers are high-risk for SMS pumping — fraudsters trigger OTPs to premium-rate destinations to generate revenue. Verify's Fraud Guard handles this automatically when enabled. If you're building custom OTP with Programmable Messaging instead, enable SMS Pumping Protection on your Messaging Service (see `twilio-messaging-services`). Always restrict geo-permissions to only countries where you have real users.
---
## CANNOT
- **No built-in channel fallback** — Must implement retry logic manually (e.g., SMS → voice → email). Use `channel_configuration` for WhatsApp→SMS only.
- **No webhook on verification completion** — Must poll `verification_checks`. Rate-limited: 60/min, 180/hr, 250/day.
- **Cannot retrieve the actual code sent** — Code is never returned in any API response. By design.
- **Sending on a new channel with the same `to` reuses the pending verification** — the same Verification SID and code are kept, just delivered over the new channel (e.g. switching `sms` → `call` for the same phone number). A different `to` (e.g. an email address) starts a separate verification. To force a fresh code on the same `to`, cancel the pending one first.
- **Cannot extend TTL on an existing verification** — Default 10 minutes, and not a per-verification or Service create/update param. Contact Twilio Support to change the default on your Service (adjustable 2 min–24 hr).
- **Verification SID deleted after approval** — Fetching an approved verification returns 404. Canceled verifications remain fetchable.
- **`auto` channel not universally available** — Returns error 60200 on accounts without Fraud Guard enabled.
- **Email channel requires Mailer configuration** — `channel: 'email'` without a configured Mailer returns error 60217.
- **No real-time delivery push notification** — Delivery status is available via List Attempts or Events API (pull-based), not via a push webhook.
- **FriendlyName rejects embedded digit strings** — avoid embedding 5 or more digits in a Service name; it can trigger error 60200. Use words.
- **Wrong code does not throw an exception** — Check returns `status: "pending"`, not an error. You must check `status === "approved"` explicitly.
- **Cannot re-check an approved verification** — Each verification is single-use. Once `approved`, subsequent checks return 404.
- **Cannot send to arbitrary numbers on trial accounts** — Trial accounts have limited verification destinations
- **Cannot customize WhatsApp OTP template** — Uses a fixed Meta authentication template
- **Cannot use WhatsApp channel for PSD2 compliance mode** — PSD2 payee/amount parameters not supported on WhatsApp
---
## Next Steps
- **Register a WhatsApp sender:** `twilio-whatsapp-manage-senders`
- **Validate phone numbers before sending:** `twilio-lookup-phone-intelligence`
- **Credential setup:** `twilio-iam-auth-setup`
© twilio · MIT · twilio/ai