sms-verification

Send and verify SMS one-time passwords with sessionId handling.

23|4|Updated May 7, 2026
One-click install
npx skills add https://github.com/qq5855144/GitHubM --skill sms-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sms-verification
Source: https://github.com/qq5855144/GitHubM/tree/main/.skills/sms-verification
Command: npx skills add https://github.com/qq5855144/GitHubM --skill sms-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill handles business SMS verification flows so you can confirm a user's phone number for security checks, identity validation, and sensitive actions without building the OTP workflow from scratch.

Core Features & Use Cases

  • Send verification codes: Trigger an SMS OTP and receive a sessionId for later validation.
  • Verify submitted codes: Check the user's code against the matching sessionId and mobile number.
  • Operational safeguards: Follow the built-in guidance for platform-managed authentication, billing-aware sending, and error handling for quota, balance, and invalid-code cases.
  • Use case: Ideal for payment confirmation, phone binding, account protection, and other non-login verification steps across web and mini program apps.

Quick Start

Send a verification SMS to the target mobile number, then verify the user's entered code with the returned sessionId to complete the check.

Frequently Asked Questions about sms-verification

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

FAQPage Schema
How do I send and verify SMS OTPs for payment confirmation?

To send and verify SMS OTPs for payment confirmation, you trigger an SMS verification code to a mobile number and receive a sessionId, then verify the user's submitted code against that sessionId to complete the security check.

What is SMS OTP verification used for in web and mini program apps?

SMS OTP verification is used for business phone verification like payment confirmation, account binding, and identity validation across web and mini program apps, handling sensitive actions without building the OTP workflow from scratch.

Can I use edge functions to handle non-login phone verification flows?

Yes, you can use edge functions to handle non-login phone verification flows by calling platform-managed gateways with an INTEGRATIONS_API_KEY and maintaining consistent sessionId handling for secure account binding and identity validation.

How do I manage sessionId and JSON request bodies when verifying mobile numbers?

You manage sessionId by capturing it when sending an SMS OTP, then passing it alongside the user's mobile number and submitted code in a JSON request body to the verification endpoint to validate the session.

What error handling do I need for SMS verification billing and quota responses?

You need error handling for SMS verification responses that checks for billing, quota, balance, and invalid-code cases, ensuring the application gracefully manages platform-managed authentication failures and validation errors.

Does Supabase support SMS verification for account binding without custom authentication?

Supabase supports SMS verification for account binding by leveraging platform-managed gateway calls with an INTEGRATIONS_API_KEY, allowing you to perform non-login identity validation without building a custom authentication workflow.