CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-voice-outbound-calls

Make outbound phone calls via Twilio's Programmable Voice REST API. Covers the full voice platform: calls.create(), answering machine detection (AMD), conference-based agent bridging, call recording, status tracking, and SIP Trunking. Use this skill for outbound calls, sales dialers, or when asking what voice APIs are available.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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, well-organized reference with strong copy-paste code in two languages, undermined slightly by some duplicated status info, no explicit pre-call validation checkpoint for an irreversible operation, and inline detail that could be offloaded to reference files.

Suggestions

Deduplicate call status transitions (currently in both the Quickstart code comment and the 'Track Call Status' section) and trim the Overview sentence that re-explains what a call requires.

Add an explicit validation checkpoint for the destructive core action — e.g., a numbered pre-call step confirming the recipient number and E.164 format before calls.create() — to lift workflow clarity.

Extract the detailed Answering Machine Detection / conference-bridging section into a reference file (e.g. references/amd-bridging.md) and link to it from the main body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean and code-driven without explaining what Twilio or a phone call is, but status transitions are repeated (Quickstart comment and 'Track Call Status') and the Overview sentence restates what a call requires, so it could be tightened further.

2 / 3

Actionability

Fully executable Python and Node.js snippets with real E.164 numbers and parameters, plus concrete error-code/fix and response-field tables — copy-paste ready guidance throughout.

3 / 3

Workflow Clarity

Patterns are sequenced (e.g., the AMD→conference bridging flow with inline comments), but because outbound calls are irreversible/destructive the absence of an explicit validate-or-confirm checkpoint before placing a call caps this at 2 per the destructive-operations rule.

2 / 3

Progressive Disclosure

Navigation is clear (capabilities table, Next Steps) and sibling-skill references are well signaled one level deep, but ~290 lines of detailed AMD/conference material live inline in SKILL.md with no bundle files split out, fitting the 'content that should be separate is inline' anchor.

2 / 3

Total

9

/

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.

A strong, third-person description that concretely enumerates capabilities, provides natural trigger terms, and explicitly states both what the skill does and when to use it. Voice is correctly third person and there is no fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'calls.create()', 'answering machine detection (AMD)', 'conference-based agent bridging', 'call recording', 'status tracking, and SIP Trunking' — matching the top anchor for naming several specific capabilities.

3 / 3

Completeness

Explicitly answers both what ('Make outbound phone calls via Twilio's Programmable Voice REST API. Covers...') and when ('Use this skill for outbound calls, sales dialers...'), satisfying the top completeness anchor.

3 / 3

Trigger Term Quality

Natural user-facing terms appear — 'outbound calls, sales dialers, or when asking what voice APIs are available' — the kind of phrasing a user would actually say, giving good keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Twilio outbound voice with distinct triggers ('Programmable Voice REST API', 'sales dialers'), making it unlikely to fire for unrelated skills.

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.