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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„rcs-agent-onboarding“ wird verwendet. Review our launch evidence. The privacy URL is supplied, but carrier approval and the Sender Profile UUID are missing.
Erwartetes Ergebnis:
- Privacy policy URL: supplied, recorded literally, and unverified.
- Carrier approval: missing.
- Sender Profile UUID: missing.
„rcs-agent-onboarding“ wird verwendet. We want RCS first and SMS fallback by listing both channels.
Erwartetes Ergebnis:
That explicit channel array creates a broadcast. Use automatic Sent routing for fallback, or pin RCS for an isolated RCS test.
„rcs-agent-onboarding“ wird verwendet. Plan a pinned RCS test for five recipients.
Erwartetes Ergebnis:
Use the pinned RCS mode and expect one RCS attempt per recipient. Record each message identifier and verify results through activities and signed webhooks.
Sicherheitsaudit
SicherAll 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.
Risikofaktoren
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/sentdm-rcs-agent-onboarding/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/sentdm-rcs-agent-onboarding?utm_source=security_passport_badge)HTML-Badge
<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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
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-Zitat
@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-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
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.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- 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.
Vermeiden
- 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.
Häufig gestellte Fragen
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?
Entwicklerdetails
Autor
sentdmLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
7c071ae4e781d8f86c5a98f874e8b9ed07d48cda
Aktualität der Wartung
8.9.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur