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

96%

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

92%Weight 40%Scale 1-3

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

A thorough, highly actionable reference with executable code, precise spec tables, and a well-sequenced onboarding workflow with a rejection-feedback loop. The only gap is progressive disclosure: everything is inline in a single long file with no bundle files to offload the detailed compliance material.

Suggestions

Move the detailed 7-part compliance onboarding (Parts 1-7 and the rejection-reasons table) into a references file (e.g. references/compliance-onboarding.md), keeping SKILL.md as an overview that links to it one level deep.

Tighten the Overview paragraph — 'delivers branded, rich messages natively in the phone's default messaging app — no separate app needed' is partly conceptual framing Claude already knows; lead with what is distinctive for this skill.

Reduce the one minor redundancy where 'RCS uses the same messages.create() API as SMS and WhatsApp' is stated in both the Overview and the 'Sending RCS Messages' section.

Dimension	Reasoning	Score
Conciseness	The body is dense, domain-specific reference material (carrier specs, rejection reasons, device caveats, copy-paste code) that Claude does not intrinsically know; the brief Overview framing earns its place rather than padding, fitting the 'lean and efficient; every token earns its place' anchor over the level-2 'could be tightened' case.	3 / 3
Actionability	Provides complete, executable Python and Node.js examples with real imports and env vars, plus concrete spec tables (e.g. '224x224px, max 50KB, PNG/JPEG', '4.5:1 contrast ratio'), matching the 'fully executable code; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The 7-part compliance onboarding and 5-step numbered registration flow give a clear sequence, and the 'Common Rejection Reasons' table plus 'Test Phase' provide an explicit feedback loop for error recovery, matching the level-3 anchor rather than the level-2 'checkpoints missing' case.	3 / 3
Progressive Disclosure	No bundle files exist, and all content (including a lengthy 7-part compliance onboarding section) lives inline in one ~228-line file; sibling-skill references in 'Next Steps' are well-signaled and one-level-deep, but inline content that could be split into a reference file places this at level-2 rather than the level-3 'appropriately split' anchor.	2 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that names concrete capabilities, includes explicit trigger guidance, and carves out a distinct niche from sibling Twilio messaging skills. It avoids vague fluff and over-claims.

Dimension	Reasoning	Score
Specificity	Names 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' — matching the 'lists multiple specific concrete actions' anchor rather than the partial level-2 example.	3 / 3
Completeness	Explicitly states what ('Send RCS Business Messages via Twilio' plus the covered subtopics) and when ('Use this skill when building RCS messaging or onboarding an RCS sender'), satisfying the level-3 'both what AND when with explicit triggers' anchor rather than the level-2 'when only implied' case.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'RCS messaging', 'RCS sender', 'Twilio', 'rich cards', 'carousels', 'SMS fallback' — with good breadth, not just jargon, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	RCS Business Messages via Twilio is a narrow, clearly-scoped niche with distinct triggers, unlikely to collide with sibling SMS/WhatsApp skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 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: 11c74d6

Reviewed: 17 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.