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

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/twilio-developer-kit/skills/twilio-cli-reference/SKILL.md

Quality

Content

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

A highly actionable command reference with strong copy-paste examples, weakened by repeated ngrok/localhost notes, missing validation for destructive operations, and an inline-only structure with no progressive disclosure to separate files.

Suggestions

Deduplicate the ngrok-not-bundled and localhost-webhook notes — state each once (e.g. in Webhook Development) and reference it from the CANNOT section instead of repeating three times.

Add a validation/verification checkpoint for irreversible operations: after `incoming-phone-numbers:create`, confirm the purchase with `phone-numbers:list`, and after `serverless:deploy`, verify the deployment URL before proceeding.

Move the detailed plugin table and the Regional & Edge Routing reference into separate files under references/ and link to them from the body, reducing the main file toward an overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command references, but the "ngrok is not bundled" note and the "cannot use localhost URLs for webhooks" limitation are each repeated across three sections, and the ngrok block has malformed list formatting with trailing spaces — it could be tightened.	2 / 3
Actionability	Nearly every section gives fully executable, copy-paste-ready commands with real flags (e.g. `twilio api:core:messages:create --from ... --to ... --body ...`) plus compact plugin and install tables, matching the 'fully executable; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Content is clearly sequenced by topic, but cost-incurring and irreversible operations like purchasing a phone number and `serverless:deploy` have no validation or verification checkpoints, which caps workflow clarity per the destructive/batch-operations guideline.	2 / 3
Progressive Disclosure	Sections are well-organized, but the ~225-line body keeps everything inline with no bundle files in references/scripts/assets and no offloaded detail; the regional-routing and plugin-reference material that could live in separate files is inline, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

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

A strong, specific description with an explicit Use-when trigger clause and good coverage of natural command-line phrasings. The only weakness is a few overly generic triggers that create mild conflict risk with other execution-oriented skills.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete actions — "installation, credential profiles, phone number provisioning, sending SMS and email, webhook configuration, local development... serverless deployment, and plugin ecosystem" — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers both 'what' (a Twilio CLI reference covering the listed capabilities) and 'when' via an explicit "Use when the developer asks to..." trigger clause, matching the 'what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	It includes natural terms a developer would say — "CLI", "command line", "terminal", "run a command" — giving good coverage of phrasings users actually use, matching the top anchor.	3 / 3
Distinctiveness Conflict Risk	The Twilio CLI niche is distinct, but generic triggers like "just do it", "set this up", and "run a command" could overlap with many command-execution skills, so it is 'somewhat specific but could still overlap' rather than conflict-free.	2 / 3
	Total	11 / 12 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: 11c74d6

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