CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

64

Quality

80%

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-organizations-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-organized, information-dense body that provides concrete Console navigation and hard Twilio-specific constraints rather than generic explanations, with clear sequences for setup, import, merging, and user management. It consistently falls just short of top marks: SSO/SCIM sections defer entirely to external docs, destructive workflows lean on preconditions instead of explicit validation steps, version-sensitive dates are outside a deprecated section, and all content is inlined with no reference-file split.

Suggestions

Add explicit verification checkpoints to destructive workflows — e.g., 'Before merging, confirm the Candidate has no verified domains and the Owner email matches the Prime's verified domain; after merging, confirm all accounts and users appear in the Prime.'

Either inline a minimal SSO/SCIM setup sequence or move the detail into a reference file instead of leaving two core sections as bare external links.

Move the signup-auto-creation dates ('since May 2024 / June 2024') into a short 'Background' or historical note so time-sensitive detail doesn't pad the operational sections, and consider splitting User Management admin actions into a referenced file.

DimensionReasoningScore

Conciseness

Dense, table-driven, and almost entirely Twilio-specific facts Claude cannot reliably know (limits, role constraints, merge rules), with little padding. Not a 5: the time-sensitive dates ('auto-created since May 2024 for new signups; since June 2024 for existing paying customers') sit outside any deprecated/old-patterns section, and the opening overview prose could be trimmed slightly.

4 / 5

Actionability

Mostly executable guidance with concrete Console navigation paths ('Console > Admin > Accounts > Create New Account', 'Admin Center > Users > Managed Users > select user > Reset Password') and specific values (limits, 24-hour reset link). Not a 5: the SSO and SCIM sections only link to external docs with no steps, and the Organizations API is named but never demonstrated despite API-level alternatives existing.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (create account, import via SID with owner email confirmation, transfer ownership, HIPAA flag, merge requirements with the failure mode 'or the merge will fail'). Not a 5: destructive operations like Organization merging and ownership transfer rely on precondition lists rather than explicit verify-before/after checkpoints, so a few validation gaps remain.

4 / 5

Progressive Disclosure

Well-organized with clear section headers, a genuinely useful CANNOT section, and clearly signaled external pointers (Twilio docs links and sibling skills in Next Steps). Not a 5: the ~175-line body keeps everything inline — detail like the User Management admin actions and the CANNOT list could live in a references file to keep SKILL.md a leaner overview, and no bundle files exist to split content across.

4 / 5

Total

16

/

20

Passed

Description

75%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, well-structured description that clearly states what the skill does and when to use it, with good Twilio-specific trigger terms and comprehensive topic coverage. It falls just short of top marks because the capability list reads as topics rather than actions, the use-when clause doesn't cover all listed capabilities, and account/subaccount coverage slightly overlaps a sibling skill.

Suggestions

Lead with action verbs instead of 'Covers...' — e.g., 'Set up Twilio Organizations, register domains, enforce SSO, configure SCIM provisioning, and merge Organizations.'

Broaden the 'Use when' clause to include the other capabilities it lists, e.g., '...or when setting up SSO/SCIM for Twilio, merging Twilio Organizations, or isolating workloads across accounts.'

Add one or two natural synonyms users would say, such as 'billing separation' or identity-provider names (Okta, Azure AD), to improve trigger recall.

DimensionReasoningScore

Specificity

Lists many specific concrete items ('roles (Owner/Admin/Standard)', 'domain registration', 'SSO enforcement', 'SCIM provisioning', and 'Organization merging') with comprehensive coverage of the domain, but the 'Covers...' list is topic nouns more than explicit action verbs, so it sits between the several-actions (4) and fully comprehensive (5) anchors.

4 / 5

Completeness

Both parts are present: a clear what ('Set up and manage Twilio Organizations for centralized account and user governance...') and an explicit when ('Use this skill when managing multiple Twilio accounts or users across teams'). Not a 5 because the when-clause is noticeably narrower than the what-clause — it omits SSO enforcement, SCIM, and org-merging triggers that the description itself covers.

4 / 5

Trigger Term Quality

Good natural keyword coverage — 'Twilio', 'Organizations', 'accounts', 'users', 'SSO', 'SCIM', 'subaccount' — phrases a user would actually say, but a few natural variants are missing (e.g., 'billing', 'consolidate accounts', identity provider names like Okta/Azure AD), matching the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

'Twilio Organizations' is a clear niche with distinct triggers, but the description explicitly covers 'the Organization > Account > Subaccount hierarchy' and account management, which overlaps the sibling twilio-account-setup skill referenced in the body's Next Steps — minor overlap risk with a closely related skill.

4 / 5

Total

16

/

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-organizations-setup/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.