CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-conversations-classic-api

Build multi-channel messaging experiences using Twilio Conversations (classic) API. Covers creating conversations, adding participants (SMS, WhatsApp, chat), sending messages, and handling webhooks. Use this skill to manage persistent multi-party or multi-channel conversations beyond single-message SMS/WhatsApp.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 skill with executable dual-language examples and a security validation checkpoint in webhooks. The main gaps are missing verification steps on batch/destructive operations and a large inlined body that could be split into reference files.

Suggestions

Add an explicit verification step after the batch 'Add Multiple Participants' loop and after conversation delete/update operations (e.g. re-fetch and confirm state) to satisfy the workflow validation requirement for batch and destructive operations.

Extract the 'Key Patterns' and 'Advanced Context' API reference material into one-level-deep reference files (e.g. PATTERNS.md, ADVANCED.md) and signal them from the overview, reducing the inlined body length.

Consider consolidating or conditionally presenting the Python/Node.js duplication to reduce token volume where the two variants are mechanically identical.

DimensionReasoningScore

Conciseness

Mostly lean executable code with no basic-concept padding, but every pattern is duplicated in Python and Node.js (~doubling length) and a few explainer sentences could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready SDK calls in two languages across all common operations (create, add participants, send media, list, remove, close, webhooks, attributes) with real parameters.

5 / 5

Workflow Clarity

A clear sequenced flow and a real validation checkpoint in the webhook (signature validate → 403), but the batch 'Add Multiple Participants' loop and delete operations lack explicit verification steps, which caps the score per the batch/destructive-operations rule.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and clearly signaled sibling-skill references, though the ~590-line body inlines all patterns with no one-level-deep reference files splitting the bulk.

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, third-person description that clearly states concrete capabilities and an explicit, contrasting use-trigger. Keyword coverage is good rather than exhaustive, and the (classic)/v2 distinction leaves slight sibling overlap.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating conversations, adding participants (SMS, WhatsApp, chat), sending messages, and handling webhooks' — giving comprehensive coverage of the domain's core operations.

5 / 5

Completeness

Explicitly answers both 'what' (build multi-channel messaging experiences covering conversations, participants, messages, webhooks) and 'when' ('Use this skill to manage persistent multi-party or multi-channel conversations beyond single-message SMS/WhatsApp').

5 / 5

Trigger Term Quality

Includes natural terms like 'multi-channel messaging', 'SMS, WhatsApp, chat', 'conversations', and 'webhooks', but misses some common synonyms a user might say (e.g. 'group chat', 'threaded messages').

4 / 5

Distinctiveness Conflict Risk

The '(classic)' API and explicit contrast against single-message SMS/WhatsApp carve a clear niche, with only minor overlap risk against a sibling Conversations v2 skill.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (599 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.