migrate-to-sent
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.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「migrate-to-sent」を使用しています。 Review a Twilio service that sends SMS and WhatsApp with ordered fallback.
期待される結果:
- 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.
「migrate-to-sent」を使用しています。 Create rollback gates for a staged Sent cutover.
期待される結果:
- 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.
セキュリティ監査
低リスク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.
確認済みのセキュリティ上の懸念 (1)
リスク要因
🌐 ネットワークアクセス (1)
🔑 環境変数 (1)
⚙️ 外部コマンド (31)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/sentdm-migrate-to-sent/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/sentdm-migrate-to-sent?utm_source=security_passport_badge)HTMLバッジ
<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>埋め込みカード
<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>学術引用 (APA · BibTeX · CFF)
APA形式の引用
sentdm. (2026). migrate-to-sent security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-migrate-to-sent/audits/1BibTeX形式の引用
@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 スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
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.
これらのプロンプトを試す
Review this repository for CPaaS dependencies. List the files and migration areas that need attention before moving to Sent.
Map our [provider] send calls, statuses, webhooks, templates, consent handling, and tenancy model to Sent v3.
Create a phased Sent cutover plan for [message classes]. Include sandbox gates, live cohorts, dual-run metrics, rollback triggers, and ownership.
Evaluate this migration plan against the Sent mapping and cutover references. Identify unsafe assumptions, missing controls, and unresolved provider differences.
ベストプラクティス
- 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.
回避
- 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.
よくある質問
Which providers does this skill cover?
Does the skill change my repository?
Can it execute the production cutover?
Why should ordered channel arrays be rewritten?
Does sandbox mode prove full migration readiness?
How are secrets handled by the scanner?
開発者情報
作成者
sentdmライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
096c7daa4d0d974771dad12d81c3d0d4688617b9
メンテナンスの新しさ
2026/9/8
利用状況
0 ダウンロード · 0 閲覧
ファイル構成