CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

twilio-whatsapp-send-message

WhatsApp messaging deep-dive reference. Covers the 24-hour service window rules (free-form vs template mode), sandbox setup for testing, template approval workflow, production sender requirements, and WhatsApp-specific error handling. For sending WhatsApp messages, use twilio-send-message instead. Use this skill when setting up WhatsApp for the first time or debugging WhatsApp-specific delivery behavior.

70

Quality

88%

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

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.

A tight, highly actionable reference: dual-language executable examples, genuine domain knowledge Claude would not reliably have (24-hour window semantics, 80 MPS cap, sandbox 3-day expiry), and a clean section structure. The main gaps are the absence of an explicit verify-after-send step and the mostly-inline layout for reference-grade detail.

Suggestions

Add a short post-send verification step (check message.status / error_code, note the 4-hour queue expiry) to close the workflow's feedback loop.

Consolidate the duplicated mode rules in the Overview prose vs. the table into a single statement.

Consider moving the Common Errors table and CANNOT limits into a references/ file if the skill grows, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is lean — tables, executable snippets, and a CANNOT list with no padding or explanations of concepts Claude already knows. The only trims available are minor: the Overview prose ("Two sending modes apply: free-form... and template... ") restates what the mode table immediately below already says.

4 / 5

Actionability

Copy-paste-ready Python and Node.js code for free-form, template, and media sends, with real env-var auth wiring, sandbox join instructions, and an error table pairing codes (63003, 63018, 63020) with concrete fixes — fully executable and covering the common cases.

5 / 5

Workflow Clarity

Prerequisites → Quickstart → Key Patterns → Common Errors forms a clear sequence, and "always check which mode is required" plus the silent-failure warning is a real checkpoint. It falls short of 5 because there is no explicit post-send verification step (e.g., check message.status/error_code before assuming delivery), and the sandbox→template-approval→production-sender path is scattered across sections rather than sequenced.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, assets/), and the ~155-line body is well-sectioned with clear headers and clearly signaled one-level-deep cross-skill links (Prerequisites, Next Steps). It scores 4 rather than 5 because the skill exceeds the self-contained threshold where everything comfortably fits inline — the error catalog and CANNOT limits are stable reference material that could live in a separate file.

4 / 5

Total

17

/

20

Passed

Description

87%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 description: concrete, well-scoped, with an explicit 'Use when' trigger and explicit conflict disambiguation against the plain-send skill. It reads as a reference coverage list rather than an action list, which is the only mild weakness.

Suggestions

Recast one or two coverage areas as actions (e.g., "Explains the 24-hour service window rules and how to switch to template mode") to sharpen the what-it-does statement.

Add one or two natural synonyms users say (e.g., "WhatsApp Business", "opt-in", "media/attachment messages") to trigger terms.

DimensionReasoningScore

Specificity

The description lists several highly concrete coverage areas — "24-hour service window rules (free-form vs template mode), sandbox setup for testing, template approval workflow, production sender requirements, and WhatsApp-specific error handling" — but frames them as topics a reference 'Covers' rather than concrete actions, so it sits just below the comprehensive-actions anchor at 5.

4 / 5

Completeness

Both questions are explicitly answered: what it does ("Covers the 24-hour service window rules... error handling") and when to use it ("Use this skill when setting up WhatsApp for the first time or debugging WhatsApp-specific delivery behavior"), with a concrete de-scoping clause for plain sends.

5 / 5

Trigger Term Quality

Natural terms users would say are present ("WhatsApp messaging", "24-hour service window", "template", "sandbox setup", "setting up WhatsApp for the first time", "debugging WhatsApp-specific delivery behavior"), but a few common variations users might say are missing (e.g., "WhatsApp Business", "opt-in", "Media").

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous and it actively disambiguates from the nearest conflicting skill: "For sending WhatsApp messages, use twilio-send-message instead" — minimal risk of triggering for the wrong skill.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/twilio-developer-kit/skills/twilio-whatsapp-send-message/SKILL.md

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.