twilio-numbers-senders

Choose the right Twilio number type and sender BEFORE building. Covers phone numbers (local, toll-free, short code, mobile), alphanumeric sender IDs, WhatsApp senders, RCS agents, international availability, and regulatory bundles. Each number type has its own compliance program — choosing wrong means rebuilding. Use this skill first.

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.

The body is highly actionable, concise, and well-sequenced, assuming Claude's competence throughout. Its main weakness is progressive disclosure: deep voice-trust detail lives inline rather than in a dedicated reference file.

Suggestions

Move the Branded Calling prerequisite stack, display-standards tables, and CNAM details into a dedicated reference file (e.g. references/voice-trust.md) and link to it from the Voice Trust section, keeping the overview to the comparison table and priority order.

Consider extracting the per-number-type compliance-program details (A2P/TFV/short-code onboarding steps) into a reference file so the overview stays a quick comparison, with the deeper registration mechanics deferred to twilio-compliance-onboarding.

Verify that sibling-skill references (twilio-compliance-onboarding, twilio-messaging-services, twilio-compliance-traffic, twilio-whatsapp-manage-senders) are correct names so navigation does not dead-end.

Dimension	Reasoning	Score
Conciseness	Dense, reference-style content that avoids explaining concepts Claude already knows; every section carries concrete constraint data (throughput, timelines, error codes) rather than filler. It leans toward over-completeness in the voice-trust section but stays non-padded.	3 / 3
Actionability	Provides concrete executable guidance: real API calls ('availablePhoneNumbers(\'US\').mobile.list() returns 404'), specific field names (voiceApplicationSid, addressRequirements values, error 30034), throughput numbers, and a copy-paste-ready decision tree.	3 / 3
Workflow Clarity	Clear sequenced lifecycle (Choose → Register → Follow traffic rules), an explicit if/then decision tree, and the layered Branded Calling stack (Layer 0→4 with prerequisites) acts as an explicit checklist; no destructive/batch loop cap applies.	3 / 3
Progressive Disclosure	Sections are well-organized and sibling-skill references are one level deep, but substantial inline detail (the full Branded Calling prerequisites/display tables, CNAM specifics) is the kind of material that belongs in a separate reference file rather than inline in an overview.	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.

The description is specific, trigger-rich, and clearly answers both what the skill does and when to use it, with a distinct Twilio-selection niche unlikely to conflict with other skills. It is concise without padding.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities — 'local, toll-free, short code, mobile', 'alphanumeric sender IDs', 'WhatsApp senders', 'RCS agents', 'international availability', 'regulatory bundles' — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what it does ('Choose the right Twilio number type and sender'; 'Covers ...') and when to use it via an explicit trigger clause ('BEFORE building', 'Use this skill first'), satisfying both what and when.	3 / 3
Trigger Term Quality	Uses natural terms a developer would say when scoping a Twilio project — 'Twilio number', 'toll-free', 'short code', 'WhatsApp senders', 'RCS', 'regulatory bundles' — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Twilio number/sender selection) with domain-specific triggers unlikely to fire for unrelated skills.	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-numbers-senders/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.