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-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «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_reportЗначок Markdown
[](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/1Цитата BibTeX
@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
Актуальность поддержки
08.09.2026
Использование
0 загрузок · 0 просмотров
Структура файлов