CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

twilio-regulatory-compliance-bundles

Manage regulatory compliance for international phone numbers. Covers what bundles are, which countries require them, how to create End-Users and Supporting Documents, evaluate and submit bundles, fix evaluation failures, update bundles when regulations change, and ISV multi-account patterns. Use this skill when provisioning numbers outside the US.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 high-quality skill body: executable end-to-end code, a clearly sequenced six-step workflow with a genuine validate-fix-retry loop, and a distinctive CANNOT section of real failure modes. Remaining weaknesses are minor — duplicated request boilerplate and all ~200 lines living inline with no reference files for deeper material.

Suggestions

Factor the repeated requests boilerplate (auth tuple, base URL, headers) into a single setup snippet and shorten subsequent examples to just the endpoint and payload.

Move the regulation-requirements detail or country-specific guidance into a references/ file (e.g., COUNTRY_REQUIREMENTS.md) linked from the body, to slim SKILL.md and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is largely lean — a compact key-concepts table, focused code, and a valuable CANNOT section — but the auth boilerplate 'auth=(account_sid, auth_token)' and the repeated '**Python**' label are duplicated across six snippets and could be factored out, leaving minor trimmable overhead short of the every-token-earns-its-place anchor.

4 / 5

Actionability

The Quickstart provides fully executable, copy-paste-ready Python covering the complete flow — querying Regulations, creating an End-User, uploading Supporting Documents, creating the Bundle with ItemAssignments, evaluating, submitting, and provisioning with bundle_sid — plus parameterized env-based credentials.

5 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with an explicit validation checkpoint and feedback loop in Step 5 ('if evaluation["status"] == "noncompliant": ... Fix the issues, then re-evaluate') before submission, exactly matching the score-5 anchor; this is not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

Sections are well organized with clear headers, external doc links, and pointers to related skills, and no bundle files exist so everything must live in SKILL.md; however, at ~200 lines with all material inline (e.g., the full quickstart and multi-account patterns), there are minor organization gaps versus the well-signaled one-level-deep references of the score-5 anchor.

4 / 5

Total

18

/

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 description that comprehensively enumerates concrete capabilities and includes an explicit 'Use this skill when...' trigger in third-person voice. Its main gaps are the missing 'Twilio' trigger term and a trigger clause that could overlap with a general number-provisioning skill.

Suggestions

Add 'Twilio' to the description (e.g., 'Manage Twilio regulatory compliance...') so users who name the provider naturally trigger this skill.

Tighten the trigger clause to reference the task more precisely (e.g., 'Use when provisioning Twilio phone numbers in countries requiring identity/ regulatory bundles') to reduce overlap with a general provisioning skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'create End-Users and Supporting Documents, evaluate and submit bundles, fix evaluation failures, update bundles when regulations change, and ISV multi-account patterns' — giving comprehensive coverage of the skill's capabilities, matching the score-5 anchor.

5 / 5

Completeness

It clearly answers both questions: 'what' via the enumerated capabilities ('Covers what bundles are, which countries require them, how to create End-Users...') and 'when' via the explicit trigger clause 'Use this skill when provisioning numbers outside the US'.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('regulatory compliance', 'bundles', 'international phone numbers', 'provisioning numbers outside the US'), but it omits the provider name 'Twilio' and common synonyms users would naturally say, so it falls short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The niche (regulatory compliance bundles for international phone numbers) is largely distinct with a specific trigger, but the unnamed provider and the broad 'provisioning numbers outside the US' phrase create minor overlap risk with a general phone-provisioning or sender-registration skill.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/twilio-developer-kit/skills/twilio-regulatory-compliance-bundles/SKILL.md

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.