rewrite-inbound

Verify webhook signatures and normalize inbound SMS payloads into internal events.

2|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/RewriteToday/skills --skill rewrite-inbound
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rewrite-inbound
Source: https://github.com/RewriteToday/skills/tree/main/rewrite-inbound
Command: npx skills add https://github.com/RewriteToday/skills --skill rewrite-inbound

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inbound SMS from providers can arrive with security risks, inconsistent payload shapes, and processing delays at scale. This Skill standardizes and secures inbound messages, turning them into a normalized event stream that downstream systems can consume reliably and safely.

Core Features & Use Cases

  • Webhook signature verification and replay protection
  • Payload normalization, media handling, and conversation correlation
  • Downstream routing and asynchronous outbound replies

Quick Start

Configure your inbound webhook endpoint, verify signatures, and enable normalization so inbound messages are processed in order and replies are sent securely.

Frequently Asked Questions about rewrite-inbound

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

FAQPage Schema
How do I verify inbound SMS webhook payloads for security?

Inbound SMS webhook verification validates provider signatures and applies replay protection. This ensures received payloads are authentic, preventing unauthorized injection and securing downstream message routing.

What is payload normalization for inbound SMS processing?

Payload normalization standardizes inconsistent inbound SMS provider formats into a uniform internal event stream. This process handles media attachments and correlates conversations for reliable downstream consumption.

How do I prevent duplicate processing of inbound SMS messages?

Preventing duplicate inbound SMS processing requires deduplication and idempotent handling. This ensures identical payloads delivered multiple times are processed once, maintaining data integrity across asynchronous workflows.

How do I configure asynchronous outbound replies for inbound SMS?

Configuring asynchronous outbound replies involves returning fast 200 responses to inbound SMS webhooks, then routing normalized events downstream. This prevents gateway timeouts and decouples reply logic from ingestion.

Can I correlate inbound SMS replies with existing conversation threads?

Inbound SMS conversation correlation matches normalized payloads to existing threads using identifier mapping. This links replies to their original outbound messages, maintaining continuous chat context across workflows.