Skills migrate-to-sent

📦

migrate-to-sent

Name: migrate-to-sent
Author: sentdm

Content revision r1 Low Risk 🌐 Network access🔑 Env variables⚙️ External commands

Plan a Safe Migration to Sent

CPaaS migrations often fail when provider concepts are copied without translation. This skill maps those differences into a phased Sent v3 cutover plan.

Supports: Claude Codex Code(CC)

📊 76 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "migrate-to-sent" from https://skillstore.io/skills/sentdm-migrate-to-sent.md and its manifest at https://skillstore.io/api/skills/sentdm-migrate-to-sent/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sentdm-migrate-to-sent.md Signed manifest GET /api/skills/sentdm-migrate-to-sent/manifest Signed lockfile GET /api/skills/sentdm-migrate-to-sent/lockfile

Test it

Using "migrate-to-sent". Review a Twilio service that sends SMS and WhatsApp with ordered fallback.

Expected outcome:

Rewrite the ordered channel list because Sent treats multiple channels as a broadcast.
Use automatic routing and preserve one logical send identifier.
Add deterministic idempotency keys before dual-run.
Verify delivery through status events rather than the accepted response.

Using "migrate-to-sent". Create rollback gates for a staged Sent cutover.

Expected outcome:

Roll back a message class when delivery falls below its agreed tolerance.
Halt immediately when duplicate production messages appear.
Stop retries when credential lockout occurs.
Keep the incumbent receiver active for in-flight callbacks.

Security Audit

Low Risk

v1 • 9/2/2026 Open versioned report

All 41 static alerts are false positives caused by documentation text, example identifiers, or Markdown backticks. The inventory scanner can expose matched source excerpts in terminal or CI logs because its redaction is limited.

Files scanned

710

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Low

scripts/inventory_scan.py:146-177 scripts/inventory_scan.py:287-289

Repository Excerpts May Reach Logs

The scanner prints matched source excerpts after limited pattern-based redaction, so unrecognized secrets or sensitive source text may enter terminal or CI logs.

The code directly prints excerpts and only masks selected credential formats. Exposure remains local to command output, which limits severity.

Risk Factors

🌐 Network access (1)

references/cutover-playbook.md:89

🔑 Env variables (1)

scripts/inventory_scan.py:58

⚙️ External commands (31)

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sentdm-migrate-to-sent/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sentdm-migrate-to-sent/security.svg)](https://skillstore.io/skills/sentdm-migrate-to-sent?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sentdm-migrate-to-sent?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sentdm-migrate-to-sent/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sentdm-migrate-to-sent.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sentdm. (2026). migrate-to-sent security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-migrate-to-sent/audits/1

BibTeX citation

@techreport{sentdm-sentdm-migrate-to-sent-2026,
  author = {sentdm},
  title = {migrate-to-sent security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/sentdm-migrate-to-sent/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "migrate-to-sent security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "sentdm"
date-released: "2026-09-02"
url: "https://skillstore.io/skills/sentdm-migrate-to-sent/audits/1"
identifiers:
  - type: other
    value: "skillstore:sentdm-migrate-to-sent:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Scope a Twilio Migration

Inventory Twilio dependencies and convert them into a prioritized Sent rewrite plan.

Design a Controlled Cutover

Define dual-run cohorts, metrics, rollback triggers, and decommission gates for a messaging platform migration.

Review Consent and Webhooks

Compare provider consent models and signature schemes before rewriting compliance-sensitive handlers.

Try These Prompts

Identify Migration Areas

Review this repository for CPaaS dependencies. List the files and migration areas that need attention before moving to Sent.

Map One Provider

Map our [provider] send calls, statuses, webhooks, templates, consent handling, and tenancy model to Sent v3.

Build a Cutover Plan

Create a phased Sent cutover plan for [message classes]. Include sandbox gates, live cohorts, dual-run metrics, rollback triggers, and ownership.

Audit Migration Readiness

Evaluate this migration plan against the Sent mapping and cutover references. Identify unsafe assumptions, missing controls, and unresolved provider differences.

Best Practices

Run the inventory scanner against the intended repository root and review every result manually.
Verify provider details against current documentation before changing customer-facing behavior.
Use sandbox validation, a small opt-in cohort, and deterministic idempotency keys before increasing traffic.

Avoid

Do not copy an ordered fallback array into Sent's channel array.
Do not treat accepted responses or provider handoff as proof of delivery.
Do not retry consent-filtered messages or clear migrated opt-out evidence.

Frequently Asked Questions

Which providers does this skill cover?

It covers Twilio, Sinch, Infobip, Vonage, and MessageBird/Bird migrations to Sent v3.

Does the skill change my repository?

No. The included scanner reads eligible files and reports migration findings without modifying source files.

Can it execute the production cutover?

No. It prepares mappings, gates, metrics, and rollback steps. Engineers must approve and perform production changes.

Why should ordered channel arrays be rewritten?

Sent treats multiple channels as broadcasts, not fallback order. Directly porting an ordered list can create duplicate messages and costs.

Does sandbox mode prove full migration readiness?

No. Sandbox validates authentication and payload shape, but live cohorts are required for routing, delivery, templates, and webhook behavior.

How are secrets handled by the scanner?

Environment files are skipped and common credential patterns are redacted. Review terminal and CI output because redaction cannot cover every secret format.