twilio-iam-auth-setup

Set up and manage Twilio authentication credentials: Auth Tokens, API keys (Standard, Main, Restricted), Access Tokens for client-side SDKs, and credential rotation. Use this skill as a prerequisite foundation before making any Twilio API calls.

Quality

80%

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

82%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.

The content is highly actionable with executable code and precise navigation, and the destructive rotation workflow carries an explicit validation checkpoint. It is efficient and well-structured, though the long single-file body could offload some reference material to bundle files.

Suggestions

Move the detailed permission-pattern tables, Access Token grant-type catalog, and the full CANNOT list into a references/ file (e.g. IAM_REFERENCE.md) linked from the relevant sections, keeping SKILL.md as a lean overview.

Trim the 'For beginners / vibe-coders' prose and collapse redundant Python/Node client-init blocks by showing one language inline and linking the other, to reduce token cost.

Add an explicit 'verify the key works' validation step to the restricted-key and API-key creation flows so every credential-issuing workflow has a checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence — it does not explain what Twilio or an API key is — but the per-pattern duplication of Python and Node blocks plus prose like 'For beginners / vibe-coders' could be trimmed, keeping it just below the lean anchor 5.	4 / 5
Actionability	Provides copy-paste-ready executable code for every credential type, exact Console navigation paths ('Console > Account > API keys & tokens > Create API key'), concrete permission patterns, and magic test numbers with their error codes, fully matching the anchor 5 example.	5 / 5
Workflow Clarity	The Auth Token rotation sequence is clearly numbered with an explicit validation checkpoint ('Once confirmed working, promote the secondary to primary') for this destructive operation, but other flows (e.g. restricted-key creation) lack an explicit verify step, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Sections are well-organized and navigable (Overview, Quickstart, Key Patterns, CANNOT, Next Steps) with clear headers and tables, but with no bundle files the ~200-line body keeps detailed reference material (permission patterns, grant types, the full CANNOT list) inline rather than split into reference files.	4 / 5
	Total	17 / 20 Passed

Description

78%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.

The description is specific, well-scoped to a distinct Twilio-auth niche, and answers both what and when, though the when-clause is a prerequisite framing rather than concrete user trigger phrases. Trigger-term coverage is strong but lacks some synonyms.

Dimension	Reasoning	Score
Specificity	Enumerates concrete credential types — 'Auth Tokens, API keys (Standard, Main, Restricted), Access Tokens for client-side SDKs, and credential rotation' — giving comprehensive coverage, but the verbs 'Set up and manage' are generic rather than distinct actions, placing it just below the anchor 5 example.	4 / 5
Completeness	Clearly states the 'what' (credential setup/management) and includes an explicit when-clause ('Use this skill as a prerequisite foundation before making any Twilio API calls'), but the 'when' is a prerequisite framing rather than concrete user-trigger phrases, so it falls short of the anchor 5 example.	4 / 5
Trigger Term Quality	Contains natural terms users would say ('Auth Tokens', 'API keys', 'Access Tokens', 'credential rotation', 'Twilio API calls') with good coverage, but misses common synonyms/extensions such as 'API key SID', 'secret', or 'client SDK tokens'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (Twilio authentication credentials) with distinct triggers and minimal overlap risk with other skills, matching the anchor 5 'clear niche with distinct triggers' example.	5 / 5
	Total	17 / 20 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-iam-auth-setup/SKILL.md
Commit: 1e28582

Reviewed: 10 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.