Skills rcs-agent-onboarding

📦

rcs-agent-onboarding

Name: rcs-agent-onboarding
Author: sentdm

Content revision r1 Safe ⚙️ External commands

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.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

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.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sentdm-rcs-agent-onboarding.md Signed manifest GET /api/skills/sentdm-rcs-agent-onboarding/manifest Signed lockfile GET /api/skills/sentdm-rcs-agent-onboarding/lockfile

Test it

Using "rcs-agent-onboarding". Review our launch evidence. The privacy URL is supplied, but carrier approval and the Sender Profile UUID are missing.

Expected outcome:

Privacy policy URL: supplied, recorded literally, and unverified.
Carrier approval: missing.
Sender Profile UUID: missing.

Using "rcs-agent-onboarding". We want RCS first and SMS fallback by listing both channels.

Expected outcome:

That explicit channel array creates a broadcast. Use automatic Sent routing for fallback, or pin RCS for an isolated RCS test.

Using "rcs-agent-onboarding". Plan a pinned RCS test for five recipients.

Expected outcome:

Use the pinned RCS mode and expect one RCS attempt per recipient. Record each message identifier and verify results through activities and signed webhooks.

Security Audit

Safe

v1 • 9/2/2026 Open versioned report

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.

Files scanned

249

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (15)

SKILL.md:21 SKILL.md:25 SKILL.md:26 SKILL.md:27 SKILL.md:30 SKILL.md:51 SKILL.md:71 SKILL.md:75 SKILL.md:80 SKILL.md:81 SKILL.md:83 SKILL.md:85 SKILL.md:93 SKILL.md:94 SKILL.md:99

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sentdm-rcs-agent-onboarding/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sentdm-rcs-agent-onboarding/security.svg)](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>

Embed card

<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>

Academic citations (APA · BibTeX · CFF)

APA citation

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 citation

@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

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

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.

Try These Prompts

Check my RCS readiness

Review my Sent RCS launch details. Ask for missing allowlisted fields and return the required three-column checklist.

Prepare the evidence packet

Organize my brand, consent, support, market, volume, profile, and message details. Mark each field supplied, missing, or unverified.

Review templates and routing

Review my text templates, suggestion chips, and routing plan. Identify unsupported features, accidental broadcast risk, and required SMS compliance.

Design a launch test matrix

Create controlled tests for pinned RCS, automatic routing, and intentional broadcast. Include expected message records, webhook evidence, counts, and approval gates.

Best Practices

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.

Avoid

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.