sent-routing-strategist
Plan Sent Message Routing
Incorrect channel choices can cause duplicate deliveries, extra charges, failed fallback, and unsafe retries. This skill explains routing decisions and diagnoses outcomes from Sent evidence.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "sent-routing-strategist" from https://skillstore.io/skills/sentdm-sent-routing-strategist.md and its manifest at https://skillstore.io/api/skills/sentdm-sent-routing-strategist/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「sent-routing-strategist」を使用しています。 We want WhatsApp first and SMS only if WhatsApp fails. Should we send both channel values?
期待される結果:
Use automatic routing by omitting the channel field or selecting Sent automatic routing. Supplying both channels creates two independent messages per recipient.
「sent-routing-strategist」を使用しています。 A message shows FAILED on WhatsApp, then newer queued and delivered events on SMS.
期待される結果:
- The WhatsApp route failed and automatic routing reused the same message identifier.
- The newer SMS delivery is the current logical outcome.
- Project state by event time and keep each route attempt in the activity history.
「sent-routing-strategist」を使用しています。 A campaign has 1,000 recipients and two channel values.
期待される結果:
The request creates 2,000 messages and potentially 2,000 charges. Confirm simultaneous delivery is intentional before sending.
セキュリティ監査
安全All 33 static findings are false positives caused by Markdown code spans or ordinary product troubleshooting guidance. The skill contains no executable commands, system reconnaissance, prompt injection, or other semantic security concerns.
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/sentdm-sent-routing-strategist/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/sentdm-sent-routing-strategist?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/sentdm-sent-routing-strategist?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sentdm-sent-routing-strategist/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/sentdm-sent-routing-strategist.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). sent-routing-strategist security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-sent-routing-strategist/audits/1BibTeX形式の引用
@techreport{sentdm-sentdm-sent-routing-strategist-2026,
author = {sentdm},
title = {sent-routing-strategist security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/sentdm-sent-routing-strategist/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: "sent-routing-strategist security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "sentdm"
date-released: "2026-09-02"
url: "https://skillstore.io/skills/sentdm-sent-routing-strategist/audits/1"
identifiers:
- type: other
value: "skillstore:sentdm-sent-routing-strategist:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Choose a routing mode
Select automatic routing, a pinned channel, or a deliberate broadcast before implementing a send.
Diagnose delivery outcomes
Use message status, channel, activities, and webhook history to explain unexpected routing behavior.
Review campaign cost
Calculate message volume and charges before approving a multi-recipient or multi-channel campaign.
これらのプロンプトを試す
I need to send [message type] to [audience]. Explain whether I should omit channel, use automatic routing, pin one channel, or broadcast.
My message ended with status [status] and channel [channel]. Explain the likely causes, evidence to inspect, and whether I should retry.
Review this ordered activity and webhook history: [events]. Reconstruct each route attempt and identify the current logical message state.
Evaluate this routing plan: [plan]. Check broadcast multiplication, channel constraints, fallback assumptions, retry rules, consent, status projection, and expected charges.
ベストプラクティス
- Prefer automatic routing unless compliance, contracts, or content require one channel.
- Use activity history and current message state before classifying a failure as final.
- Calculate recipients multiplied by channels before approving a multi-channel request.
回避
- Do not treat the channel array as an ordered fallback list.
- Do not retry FILTERED messages or duplicate SCHEDULED messages.
- Do not infer the attempted route from the initial automatic-routing response.
よくある質問
Does the channel array define fallback order?
When should I pin a channel?
Can a FAILED message later deliver?
What does channel auto mean?
Should I retry a FILTERED message?
How do I estimate broadcast cost?
開発者情報
作成者
sentdmライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
096c7daa4d0d974771dad12d81c3d0d4688617b9
メンテナンスの新しさ
2026/9/8
利用状況
1 ダウンロード · 0 閲覧
ファイル構成