send-sms

Name: send-sms
Availability: InStock
Author: Rewrite

Send idempotent SMS messages with batching and webhook-driven delivery state.

2|1|Updated Feb 18, 2026

Search Tags:#queue #webhooks #idempotency #delivery #sms #outbound

Ready to run

npx skills add https://github.com/RewriteToday/skills --skill send-sms-rewritetoday

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: send-sms
Source: https://github.com/RewriteToday/skills/tree/main/send-sms
Command: npx skills add https://github.com/RewriteToday/skills --skill send-sms-rewritetoday

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This capability enables production-grade outbound SMS delivery by ensuring idempotent, reliable messaging at scale, reducing duplicate sends and fragile delivery logic.

Core Features & Use Cases

Idempotent Sends: Ensure each business action maps to a unique, deduplicated outbound message.
Batching & Queueing: Support high-volume campaigns via bounded jobs and queue-backed fan-out.
Delivery Lifecycle: Track and reconcile provider events with internal state using a robust webhook-driven flow.
SDK & REST Adoption: Works with Node/Go/Types SDKs or REST APIs for diverse environments.
Observability & Governance: Persist metadata, add correlation IDs, and surface delivery metrics for reliability.

Quick Start

Use the SendSms workflow to implement outbound messaging in your app with a simple integration and test message.

Frequently Asked Questions about send-sms

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

FAQPage Schema

How do I prevent duplicate outbound SMS messages in high-volume campaigns?▼

Idempotent SMS delivery ensures each business action maps to a unique, deduplicated outbound message. By applying idempotency keys and persisting send state, the workflow prevents duplicate sends even during retries or network failures in high-volume campaigns.

What is the best way to track outbound SMS delivery lifecycle using webhooks?▼

Tracking the SMS delivery lifecycle involves reconciling provider webhook events with your internal delivery state. This webhook-driven flow updates message statuses persistently, ensuring accurate delivery tracking and observability for both transactional and campaign messages.

Can I send outbound SMS using Node or Go SDKs with queue-backed batching?▼

Yes, outbound SMS workflows support Node, Go, and Types SDKs alongside REST APIs. High-volume campaigns are handled through bounded jobs and queue-backed fan-out, enabling reliable batch processing and scalable message delivery.

How do I validate phone numbers and define a send contract for transactional SMS?▼

Defining a send contract and validating phone numbers are prerequisite steps for reliable transactional SMS. The workflow enforces number validation and contract definitions before dispatch, ensuring messages meet delivery state management and governance requirements.

Why does my outbound SMS delivery logic fail at scale and how do I fix it?▼

Outbound SMS delivery fails at scale due to fragile state management and missing idempotency. Fix this by enforcing idempotency keys, persisting delivery metadata, and using a webhook-driven flow to reconcile provider events with internal state for reliable messaging.