rewritetoday/send-sms
send-sms/SKILL.md
Production SMS delivery workflow for Rewrite. Use when the agent needs to send transactional or campaign SMS, manage Rewrite contacts or segments, implement batching, enforce idempotency, use templates and scheduling, and integrate the official Rewrite SDKs, REST client, CLI, or ecosystem packages.
$ install --global
skillsauthnpx skillsauth add rewritetoday/skills send-smsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 4, 2026, 5:18 AM206.0s8 files scanned
SKILL.md
- name:
- send-sms
- description:
- Production SMS delivery workflow for Rewrite. Use when the agent needs to send transactional or campaign SMS, manage Rewrite contacts or segments, implement batching, enforce idempotency, use templates and scheduling, and integrate the official Rewrite SDKs, REST client, CLI, or ecosystem packages.
Send SMS With Rewrite
Implement outbound SMS against the current public Rewrite API contract.
Workflow
- Install client dependencies from
references/installation.md. - Choose one target shape:
- direct number:
to - stored contact:
contactas contact ID or exact contact name
- Choose one content shape:
- inline body: target plus
content - template body: target plus
templateIdplusvariables
- Use
/contactswhen recipients need stable metadata such asname,channel, or per-contacttags. - Use
/segmentsand/segments/:id/contactsto maintain reusable audiences. There is no direct segment-send endpoint; list the segment contacts, then call/messagesor/messages/batch. - Add optional
tags,scheduledAt, andsegmentationonly when required by the flow. - Attach
Idempotency-Keyto every create/send action. - Persist the accepted message ID plus the returned
analysis. - Register webhooks before production rollout and treat delivery as asynchronous.
- Use batch sends only for 1 to 100 messages per request.
Delivery Design Rules
- Use Brazilian
+55E.164 numbers on the public API unless the project explicitly supports international numbers. - Prefer
contactover rawtowhen the same recipient will be reused, tagged, or segmented. - If you target
contactby name, keep the name unique and stable per project because lookup is exact. - Sending with raw
tostill ensures a Rewrite contact exists for that phone number. - Prefer templates for repeated or locale-aware flows.
- Keep OTP and transactional content short and watch segmentation counts.
- Retry only
429and transient5xx. - Treat
400,401, and commercial403blocks as non-retryable until fixed. - Do not require
message.deliveredfor critical workflows; it is still WIP in the public docs.
Quick Example
Single SMS send via REST:
curl -X POST https://api.rewritetoday.com/v1/messages \
-H "Authorization: Bearer $REWRITE_API_KEY" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"to": "+5511999999999", "content": "Your code is 4821"}'
Resource Map
- Install, SDK selection, CLI, and ecosystem packages:
references/installation.md - Contacts, segments, and audience orchestration:
references/contacts-and-segments.md - Single-send implementation patterns:
references/single-sms-examples.md - Batch and queue patterns:
references/batch-sms-examples.md - Template i18n rules:
references/template-i18n.md - Delivery and webhook lifecycle:
references/delivery-lifecycle.md - Production guardrails:
references/best-practices.md
Output Contract
Persist or return the accepted response. Expected shape:
{
"id": "msg_abc123",
"status": "accepted",
"to": "+5511999999999",
"createdAt": "2026-04-06T12:00:00Z",
"analysis": { "encoding": "GSM-7", "characters": 22, "segments": 1 },
"idempotencyKey": "550e8400-e29b-41d4-a716-446655440000",
"tags": []
}
Related Skills
rewritetoday/sms-best-practices
development
VerifiedTrustedCommunity
General SMS best-practices guide for Rewrite-based systems. Use when the agent needs to define SMS architecture, contacts and segments strategy, deliverability, templates, retries, observability, webhook handling, or rollout guardrails before or alongside implementation.
2SKILL.mdUpdated May 4, 2026
rewritetoday/rewrite-inbound
development
VerifiedTrustedCommunity
Rewrite webhook ingestion workflow for your application. Use when the agent needs to configure Rewrite webhooks, verify signatures, parse and normalize event payloads, handle retries and dedupe, inspect delivery logs, and route delivery or OTP events safely.
2SKILL.mdUpdated May 4, 2026
rewritetoday/agent-sms-inbox
development
VerifiedTrustedCommunity
Secure SMS agent workflow for building a text message chatbot, messaging agent, or SMS bot on Rewrite. Covers LLM-driven replies over application-owned inbound conversations with prompt-injection defense, action policy gates, risk-level escalation, and outbound send controls.
2SKILL.mdUpdated May 4, 2026
rewritetoday/rewrite
tools
VerifiedTrustedCommunity
Rewrite platform router for API, SDK, CLI, contacts, segments, webhooks, templates, and AI workflows. Use when the agent needs to send SMS, manage Rewrite contacts or segments, handle Rewrite webhook events, work with official Rewrite SDKs/packages, or build application-owned agent flows on top of Rewrite.
2SKILL.mdUpdated May 4, 2026