CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-email-send

Use when the caller has Twilio credentials (Account SID + Auth Token or API Key SID + Secret) and needs to send email via comms.twilio.com/v1/Emails. This is Twilio-native email — NOT SendGrid. Do NOT use if the caller has a SendGrid API key (SG.-prefix) — use twilio-sendgrid-email-send instead. Covers single sends, batch sends up to 10,000 recipients, Liquid personalization, operation tracking, and error handling.

76

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

Well-structured, actionable, and token-efficient content built around executable examples and a clear CANNOT list. The main gap is the absence of an explicit validation/retry checkpoint in the batch send-and-track workflow, which the rubric caps at 2 for batch operations.

Suggestions

Add an explicit validation checkpoint to the send workflow: after polling operationLocation, instruct checking the Operation status and branching on failure (e.g., retry with backoff on 429/503, surface rejected recipients) before declaring success.

Note that limits like '10,000 recipients' and '10MB message size' are restated across the comparison table, the Batch section, and CANNOT — consolidate to a single source to tighten token use.

Clarify how a caller maps a polled Operation status (queued/processing/succeeded/failed) to recipient-level delivery outcomes, since 202 only confirms acceptance.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept-explanation fluff — it assumes Claude knows what email/auth are and spends tokens only on the endpoint, payloads, limits, and pitfalls, with the comparison table earning its place for routing.

3 / 3

Actionability

Provides a fully executable curl example with real endpoint, headers, JSON body, and Basic auth, plus copy-paste batch and Liquid examples and an error table with concrete remediation actions.

3 / 3

Workflow Clarity

The Operation Tracking steps sequence submit → poll → track, but for a batch-send (up to 10,000) irreversible operation there is no explicit validation checkpoint or failure-feedback loop, so it is capped at 2 per the rubric.

2 / 3

Progressive Disclosure

A single self-contained file organized into clearly navigable sections (Overview, Prerequisites, Auth, Send, Batch, Liquid, Tracking, Errors, CANNOT, Next Steps) with no nested references and no bundle files needed.

3 / 3

Total

11

/

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 tightly written description that names concrete capabilities, provides an explicit trigger, and aggressively distinguishes itself from the sibling SendGrid skill. It satisfies the what/when/conflict criteria without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'single sends, batch sends up to 10,000 recipients, Liquid personalization, operation tracking, and error handling' — matching the anchor for enumerating specific capabilities.

3 / 3

Completeness

Explicit 'Use when the caller has Twilio credentials ... and needs to send email' answers both what (sends, batch, personalization, tracking, errors) and when with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms a user would say — 'send email', 'Twilio', 'email', 'batch sends' — alongside the credential context, giving good coverage rather than relying on jargon.

3 / 3

Distinctiveness Conflict Risk

Clearly carves a niche — 'NOT SendGrid', redirects 'SG.'-prefix keys to twilio-sendgrid-email-send — making misrouting unlikely.

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.