CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-organizations-setup

Set up and manage Twilio Organizations for centralized account and user governance. Covers the Organization > Account > Subaccount hierarchy, roles (Owner/Admin/Standard), managed vs independent accounts, domain registration, SSO enforcement, SCIM provisioning, and Organization merging. Use this skill when managing multiple Twilio accounts or users across teams.

76

Quality

93%

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

87%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 lean, actionable, and well-structured, but destructive workflows (merge, ownership transfer, HIPAA) omit explicit validation/verification steps, capping workflow clarity.

Suggestions

Add an explicit verification checkpoint after Organization merging (e.g., confirm transferred accounts/users appear in Prime before treating the merge as complete).

For account ownership transfer, add a confirm/verify step that the new owner has access before removing the prior owner.

For HIPAA designation, add a validation step that the BAA is executed and the flag is reflected per account before relying on it.

DimensionReasoningScore

Conciseness

Dense, table-driven body that assumes Claude's competence and adds only domain specifics Claude lacks (auto-creation dates, limits); prose is minimal and earns its place.

3 / 3

Actionability

Gives concrete Console navigation paths ("Console > Admin > Accounts > Create New Account"), exact limits (10 accounts/Org, 1,000 subaccounts), and hard requirements (verified domain match) — copy-ready guidance for a UI workflow.

3 / 3

Workflow Clarity

Steps for ownership transfer, merging, and HIPAA flagging are sequenced, but destructive operations lack explicit validation checkpoints; per the rubric this caps the score at 2.

2 / 3

Progressive Disclosure

A single well-organized SKILL.md with clearly labeled sections and one-level cross-links to sibling skills; no deep reference nesting, appropriate for a self-contained skill.

3 / 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, third-person, and answers both what and when with a clear trigger clause, hitting all anchor criteria for the top level.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and objects — "Set up and manage Twilio Organizations", "domain registration, SSO enforcement, SCIM provisioning, and Organization merging" alongside the role and hierarchy model.

3 / 3

Completeness

Explicitly states both what ("Set up and manage... governance") and when ("Use this skill when managing multiple Twilio accounts or users across teams").

3 / 3

Trigger Term Quality

Natural terms a user would say appear directly — "managing multiple Twilio accounts or users across teams" — covering the common phrasings for this need.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Twilio Organizations governance with distinct triggers, making overlap with adjacent skills unlikely.

3 / 3

Total

12

/

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.