twilio-identity-verification-advisor

Plans Twilio Verify and Lookup architectures for identity verification and fraud prevention workflows.

5.3k|765|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/openai/plugins --skill twilio-identity-verification-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: twilio-identity-verification-advisor
Source: https://github.com/openai/plugins/tree/main/plugins/twilio-developer-kit/skills/twilio-identity-verification-advisor
Command: npx skills add https://github.com/openai/plugins --skill twilio-identity-verification-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Choosing the right identity verification approach is hard: developers must pick channels (SMS, WhatsApp, voice, push, TOTP, passkeys), assess fraud risk, and decide between Twilio Verify and custom OTP logic. This Skill qualifies the developer's needs and recommends the right Twilio Verify + Lookup architecture.

Core Features & Use Cases

  • Intent Qualification: Asks four essential questions about verification timing, channels, fraud risk level, and user base geography before recommending an architecture.
  • Verification Ladder: Maps requests to three sophistication levels, from basic OTP via the Verify API, to multi-channel fallback, to risk-adaptive verification using Lookup line type and SIM swap intelligence.
  • Fraud Prevention Guidance: Recommends enabling Fraud Guard and SMS pumping protection, and pairing Verify with Lookup for KYC-regulated or high-value transaction flows.
  • Use Case: A developer says "I need to add phone verification to my signup flow." The Skill qualifies their fraud risk and geography, then recommends Verify API with SMS OTP plus Lookup line type intelligence, and lists the exact follow-up skills to install.

Quick Start

Ask the assistant to recommend a Twilio verification architecture for adding phone verification to your signup flow.

Frequently Asked Questions about twilio-identity-verification-advisor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add phone verification to my signup flow with Twilio?

Use the Twilio Verify API to start a verification with channel=sms and then check the code the user enters. Verify handles code generation, expiry, rate limiting, and fraud protection, so you avoid building custom OTP logic with the Programmable Messaging API.

Twilio Verify API vs Programmable Messaging API for OTP?

Verify is highly recommended for OTP because it provides managed code generation, delivery, expiry, replay protection, Fraud Guard, and multi-channel support. Use Programmable Messaging only when you need full control over message content or custom routing logic.

Which verification channel should I use: SMS, WhatsApp, voice, or push?

SMS offers universal reach and is the default for signup and login. WhatsApp can be more cost-effective internationally, push gives the best UX for mobile app users, voice works as an accessibility fallback, and TOTP or passkeys suit high-security enterprise cases.

How do I prevent SMS pumping fraud in Twilio verification?

Enable Fraud Guard on your Verify Service, which is included at no extra cost and protects against SMS pumping. For higher risk flows, add Lookup line type intelligence to flag VoIP numbers and SIM swap checks before sending codes.

When should I use Twilio Lookup before sending a verification code?

Use Lookup before Verify for signups to confirm the number is real, and for high-value transactions to check line type. KYC-regulated businesses should add SIM swap checks, while routine 2FA on previously verified numbers can skip Lookup.

Why does a wrong Twilio Verify code not return an error?

A wrong verification code returns status pending with valid=false rather than an error, which is expected behavior. Only the sixth consecutive wrong attempt throws error 60202, so your code should handle the pending status gracefully.