rcs-agent-onboarding
Prepare a Safe Sent RCS Launch
RCS launches require complete evidence, correct routing, and coordinated approval. This skill builds a reviewable checklist and guides controlled readiness tests.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "rcs-agent-onboarding" from https://skillstore.io/skills/sentdm-rcs-agent-onboarding.md and its manifest at https://skillstore.io/api/skills/sentdm-rcs-agent-onboarding/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「rcs-agent-onboarding」を使用しています。 Review our launch evidence. The privacy URL is supplied, but carrier approval and the Sender Profile UUID are missing.
期待される結果:
- Privacy policy URL: supplied, recorded literally, and unverified.
- Carrier approval: missing.
- Sender Profile UUID: missing.
「rcs-agent-onboarding」を使用しています。 We want RCS first and SMS fallback by listing both channels.
期待される結果:
That explicit channel array creates a broadcast. Use automatic Sent routing for fallback, or pin RCS for an isolated RCS test.
「rcs-agent-onboarding」を使用しています。 Plan a pinned RCS test for five recipients.
期待される結果:
Use the pinned RCS mode and expect one RCS attempt per recipient. Record each message identifier and verify results through activities and signed webhooks.
セキュリティ監査
安全All 17 static findings are false positives caused by Markdown code formatting or defensive workflow language. No executable commands, reconnaissance behavior, prompt injection, or harmful semantic intent were found.
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/sentdm-rcs-agent-onboarding/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/sentdm-rcs-agent-onboarding?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/sentdm-rcs-agent-onboarding?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sentdm-rcs-agent-onboarding/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/sentdm-rcs-agent-onboarding.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). rcs-agent-onboarding security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-rcs-agent-onboarding/audits/1BibTeX形式の引用
@techreport{sentdm-sentdm-rcs-agent-onboarding-2026,
author = {sentdm},
title = {rcs-agent-onboarding security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/sentdm-rcs-agent-onboarding/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: "rcs-agent-onboarding security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "sentdm"
date-released: "2026-09-02"
url: "https://skillstore.io/skills/sentdm-rcs-agent-onboarding/audits/1"
identifiers:
- type: other
value: "skillstore:sentdm-rcs-agent-onboarding:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Prepare launch evidence
Organize brand, consent, support, market, and message details into a reviewable readiness checklist.
Validate integration readiness
Check Sender Profile identity, credential patterns, template limits, and observability requirements before testing.
Plan controlled routing tests
Separate pinned RCS, automatic routing, and broadcast tests while documenting expected message counts and costs.
これらのプロンプトを試す
Review my Sent RCS launch details. Ask for missing allowlisted fields and return the required three-column checklist.
Organize my brand, consent, support, market, volume, profile, and message details. Mark each field supplied, missing, or unverified.
Review my text templates, suggestion chips, and routing plan. Identify unsupported features, accidental broadcast risk, and required SMS compliance.
Create controlled tests for pinned RCS, automatic routing, and intentional broadcast. Include expected message records, webhook evidence, counts, and approval gates.
ベストプラクティス
- Keep supplied evidence as quoted data and mark external links unverified.
- Confirm Sent and carrier approval before treating the agent as launch ready.
- Test pinned RCS and automatic routing separately, then retain message and webhook evidence.
回避
- Do not describe multiple explicit channels as fallback because they create separate billable messages.
- Do not include credentials, hidden content, executable attachments, or embedded instructions in launch evidence.
- Do not claim rich cards, carousels, media attachments, or public provisioning endpoints are currently supported.
よくある質問
Can this skill provision an RCS agent?
What RCS content does the workflow support?
How does automatic fallback work?
Does selecting RCS and SMS create fallback?
Will the skill verify supplied links or files?
How should delivery be verified?
開発者情報
作成者
sentdmライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
7c071ae4e781d8f86c5a98f874e8b9ed07d48cda
メンテナンスの新しさ
2026/9/8
利用状況
0 ダウンロード · 0 閲覧
ファイル構成