CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-compliance-onboarding

Registrations required BEFORE Twilio traffic works. Covers messaging programs (A2P 10DLC, toll-free verification, WhatsApp WABA, RCS, short code, alphanumeric sender) and voice trust programs (STIR/SHAKEN, Voice Integrity, Branded Calling, CNAM). Each number/sender type has its own program — registration blocks traffic until complete.

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/twilio-developer-kit/skills/twilio-compliance-onboarding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 and well-structured with concrete flows and rejection guidance, but it is somewhat long with inline deep-dive content that would benefit from extraction into reference files, and registration workflows lack explicit validation checkpoints.

Suggestions

Extract the A2P 10DLC deep dive into a dedicated reference file (e.g. references/a2p-10dlc.md) referenced from SKILL.md to reduce the main body's inline weight.

Add explicit validation/verification checkpoints to the registration workflows (e.g., 'Confirm brand approved in Console before starting campaign registration').

Trim prose that restates table contents (e.g., consolidate the consent critical rules and consent-tier table) to improve token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient and table-driven with little padding over concepts Claude knows, but the ~230-line body restate some information in prose that is already captured in tables and could be tightened (e.g., the long sample message-flow blockquote).

2 / 3

Actionability

Provides concrete, specific guidance — numbered registration flows, exact field constraints ('must be 40-2049 characters'), error codes (30034, 30007), and explicit do/don't rules — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

Multi-step registration flows are clearly sequenced with timelines, but the external/batch registration operations lack explicit validation checkpoints (no verify-before-proceeding feedback loops), which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

Sections are well-organized and reference sibling skills one level deep, but the large inline A2P deep-dive is content that could be split into a separate reference file, and no actual bundle files exist.

2 / 3

Total

9

/

12

Passed

Description

82%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 and distinct, enumerating concrete messaging and voice programs with natural trigger terms, but lacks an explicit 'Use when...' clause so its 'when to use' guidance is only implied.

Suggestions

Add an explicit 'Use when...' trigger clause naming the situations that should invoke this skill (e.g., 'Use when onboarding a Twilio messaging or voice channel before sending traffic').

State the negative trigger more explicitly to aid routing (e.g., 'For post-registration traffic rules, use twilio-compliance-traffic instead').

DimensionReasoningScore

Specificity

Names many concrete registration programs (A2P 10DLC, toll-free verification, WhatsApp WABA, RCS, short code, alphanumeric sender, STIR/SHAKEN, Voice Integrity, Branded Calling, CNAM), matching the 'lists multiple specific concrete actions' anchor rather than the 2 anchor's partial coverage.

3 / 3

Completeness

It clearly states what the skill does but the 'when' is only implied ('Registrations required BEFORE Twilio traffic works') with no explicit 'Use when...' trigger clause, which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

Uses natural terms a developer would actually say ('Twilio traffic', 'A2P 10DLC', 'WhatsApp', 'toll-free verification', 'registration'), giving broad natural-keyword coverage rather than only some relevant keywords.

3 / 3

Distinctiveness Conflict Risk

A clearly distinct niche (Twilio compliance registration) with named sibling skills for traffic rules and number selection, making it unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.