twilio-rcs-messaging

Send RCS Business Messages via Twilio. Covers compliance onboarding (7-part US process), sender profile setup, sending rich cards and carousels, SMS fallback, device support (Android + iOS 18 caveats), and common errors. Use this skill when building RCS messaging or onboarding an RCS sender.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable body with concrete code, exact asset specs, and a clearly sequenced onboarding workflow. Trim the conceptual Overview and reduce overlap between the error/rejection/CANNOT sections, and consider splitting the 7-part compliance onboarding into a dedicated reference file.

Suggestions

Tighten the Overview paragraph — remove conceptual framing of what RCS is and lead with the actionable essentials, since Claude already understands messaging channels.

Dedupe the Common Errors table, the Common Rejection Reasons table, and the CANNOT list so each failure mode appears in one canonical place with a cross-reference.

Move the detailed 7-part compliance onboarding into a separate reference file (e.g. references/compliance-onboarding.md) and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with dense tables and exact specs (224x224px, 50KB, 4.5:1 contrast), but the Overview explains RCS conceptually and the Common Errors / CANNOT / Common Rejection Reasons sections repeat some material.	4 / 5
Actionability	Copy-paste-ready Python and Node.js send examples plus concrete asset specs cover the common cases; rich cards are deferred to another skill rather than shown inline, a minor gap.	4 / 5
Workflow Clarity	The Registration Flow is a clear 5-step sequence with checkpoints (Test Phase, specialist review, per-carrier approval gate, go-live); not a destructive/batch operation, so the 3-cap does not apply, though a few verification checkpoints are implicit.	4 / 5
Progressive Disclosure	Well-sectioned with clearly signaled sibling-skill links and external doc URLs in Next Steps and inline; no nested references. The long inline 7-part onboarding could plausibly live in a separate reference file, leaving a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states capabilities and gives explicit trigger guidance for when to invoke the skill. Minor gains are possible by adding a couple of natural synonyms and sharpening the distinction from adjacent Twilio messaging skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "compliance onboarding (7-part US process), sender profile setup, sending rich cards and carousels, SMS fallback, device support (Android + iOS 18 caveats), and common errors" — with comprehensive coverage rather than generic phrasing.	5 / 5
Completeness	Explicitly answers both what it does (the listed capabilities) and when to use it ("Use this skill when building RCS messaging or onboarding an RCS sender") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ("RCS Business Messages", "RCS messaging", "onboarding an RCS sender", "rich cards", "carousels", "SMS fallback"), but a few natural synonyms (e.g. "RCS chat", "verified messaging") are missing.	4 / 5
Distinctiveness Conflict Risk	Has a clear RCS niche with distinct triggers, but minor overlap risk with closely related Twilio SMS/WhatsApp/messaging skills that share the same messages.create() API.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/twilio-developer-kit/skills/twilio-rcs-messaging/SKILL.md
Commit: d416fd5

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.