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.
Instalar com meu Agente
Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.
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.Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.
Recursos legíveis por agentes
Use estes links quando um agente de IA, crawler ou script precisar de contexto limpo em vez de ler a página completa.
Testar
Usando "rcs-agent-onboarding". Review our launch evidence. The privacy URL is supplied, but carrier approval and the Sender Profile UUID are missing.
Resultado esperado:
- Privacy policy URL: supplied, recorded literally, and unverified.
- Carrier approval: missing.
- Sender Profile UUID: missing.
Usando "rcs-agent-onboarding". We want RCS first and SMS fallback by listing both channels.
Resultado esperado:
That explicit channel array creates a broadcast. Use automatic Sent routing for fallback, or pin RCS for an isolated RCS test.
Usando "rcs-agent-onboarding". Plan a pinned RCS test for five recipients.
Resultado esperado:
Use the pinned RCS mode and expect one RCS attempt per recipient. Record each message identifier and verify results through activities and signed webhooks.
Auditoria de segurança
SeguroAll 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.
Fatores de risco
Compartilhar e citar este relatório
Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.
Copiar link do relatório
https://skillstore.io/skills/sentdm-rcs-agent-onboarding/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/sentdm-rcs-agent-onboarding?utm_source=security_passport_badge)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>Cartão incorporável
<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>Citações acadêmicas (APA · BibTeX · CFF)
Citação 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/1Citação 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"
Pontuação do Skillstore
Por que esta pontuação Confiança das evidências: MédioO que você pode criar
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.
Teste estes prompts
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.
Boas práticas
- 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.
Evitar
- 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.
Perguntas frequentes
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?
Detalhes do desenvolvedor
Autor
sentdmLicença
MIT
Revisão da Skillstore
r1
Aviso de versão
O autor não declarou uma versão.
Referência
7c071ae4e781d8f86c5a98f874e8b9ed07d48cda
Atualidade da manutenção
08/09/2026
Uso
0 downloads · 0 visualizações
Estrutura de arquivos