twilio-cli-reference

Twilio CLI reference for managing Twilio resources from the terminal. Covers installation, credential profiles, phone number provisioning, sending SMS and email, webhook configuration, local development with a tunneling service, debugging with watch and logs, serverless deployment, and plugin ecosystem. Use when the developer asks to "just do it", "set this up", "run a command", mentions "CLI", "command line", or "terminal", or when an AI agent can execute a task directly instead of writing application code.

Quality

82%

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

76%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 highly actionable, well-structured command reference with copy-paste ready examples. Its weaknesses are a duplicated/malformed ngrok note affecting conciseness and the absence of validation checkpoints for billable operations like number purchasing.

Suggestions

Fix the malformed ngrok note (lines 122-125) and remove the duplicate in the CANNOT section — state the ngrok-not-bundled requirement once, cleanly.

Add a brief verification step for billable/irreversible operations (e.g., confirm number purchase with `twilio phone-numbers:list` after `create`, or note that purchasing incurs cost before running the command).

Make the Linux apt install path executable like the other platforms rather than deferring to an external 'getting-started/install' reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples with brief comments, but the ngrok 'not bundled' note is duplicated — once as a malformed ASCII block (lines 122-125) and again in the CANNOT section (lines 226-227) — which is trimmable redundancy.	4 / 5
Actionability	Provides copy-paste ready, fully executable commands across install, auth, phone numbers, SMS, email, webhooks, debugging, and deployment, covering the common cases with specific flags and example values.	5 / 5
Workflow Clarity	Content is organized into a logical topic sequence (install → auth → numbers → send → debug → deploy), but billable/destructive operations like number purchasing and serverless deploy lack any validation or verification checkpoints, capping the score per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep navigation via the Next Steps links to sibling skills and no nested references; no bundle files exist, so structure is judged on the inline organization, which is good with minor gaps.	4 / 5
	Total	16 / 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, specific description that clearly states capabilities and provides explicit trigger guidance. The main weakness is reliance on generic trigger phrases ('just do it', 'set this up') that dilute distinctiveness.

Suggestions

Tighten trigger phrases toward Twilio-specific intent (e.g., 'send an SMS from the terminal', 'provision a Twilio number', 'deploy a Twilio Function') rather than generic 'just do it' / 'set this up'.

Consider adding the keyword 'Twilio' into the trigger clause so the description fires on Twilio-mentioning requests, not just generic CLI requests.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'installation, credential profiles, phone number provisioning, sending SMS and email, webhook configuration, local development with a tunneling service, debugging with watch and logs, serverless deployment, and plugin ecosystem' — giving comprehensive coverage of the CLI's capabilities.	5 / 5
Completeness	Explicitly answers both what ('managing Twilio resources from the terminal... Covers installation...') and when ('Use when the developer asks to... mentions CLI, command line, or terminal...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a user would say — 'CLI', 'command line', 'terminal', 'run a command' — but mixes in generic phrases like 'just do it' and 'set this up' that are not skill-specific, leaving it just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Twilio CLI niche is distinct and clearly bounded, but generic triggers like 'just do it' and 'set this up' create minor overlap risk with other CLI or setup skills.	4 / 5
	Total	18 / 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-cli-reference/SKILL.md
Commit: 1e28582

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