CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-communications

Basic pattern for sending SMS messages with Twilio. Handles the fundamentals: phone number formatting, message delivery, and delivery status callbacks.

48

Quality

51%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/twilio-communications/SKILL.md

The canonical home for this skill is twilio-communications in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is well-structured into three Twilio patterns with real code, but every code example is truncated and therefore non-executable, the Sharp Edges table is malformed with placeholder cells, and the When to Use section is generic boilerplate. Progressive disclosure is limited because all content lives in one large inline file.

Suggestions

Complete the three truncated code blocks so each example is a full, copy-paste-executable unit (finish _handle_error, check_verification, and the IVR voicemail branch).

Fix the Sharp Edges table: replace every placeholder 'Issue' cell with the real issue name and convert the malformed '## ...' header-as-solution cells into plain solution text.

Replace the generic 'When to Use' boilerplate with skill-specific guidance, and consider splitting each Twilio pattern into its own reference file so SKILL.md stays an overview.

DimensionReasoningScore

Conciseness

Mostly focused prose with useful key-consideration bullets, but includes marketing filler ('saved customers $82M+ blocking 747M attempts', Google 2FA stats) that does not earn its tokens.

3 / 5

Actionability

Real Python is provided, but all three code blocks are truncated mid-definition ('def _handle_error(self, error: Twilio', 'R', '"Please leave a message after '), so nothing is copy-paste executable.

3 / 5

Workflow Clarity

The content is organized as pattern snippets rather than a sequenced workflow, and there are no validate->fix->retry checkpoints at the process level despite some in-code validation.

3 / 5

Progressive Disclosure

The ~290-line file is well-sectioned by headers but is monolithic with no bundle references, and the three large patterns are inlined where they could be split into separate reference files.

3 / 5

Total

12

/

20

Passed

Description

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

The description is third-person and names a concrete Twilio SMS niche, but it omits any explicit 'when to use' trigger guidance and is missing common synonyms. It is distinct but not fully complete or comprehensive in trigger coverage.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when sending SMS notifications, transactional messages, or setting up delivery status callbacks via Twilio').

Include natural user synonyms like 'text messages' and 'texting' alongside 'SMS' to broaden trigger term coverage.

Reconcile scope: the body covers Verify/2FA and IVR patterns the description never mentions — either reflect that scope or clarify this skill is SMS-only.

DimensionReasoningScore

Specificity

Names the domain (Twilio SMS) and concrete sub-actions ('phone number formatting, message delivery, and delivery status callbacks'), but the 'Handles the fundamentals' framing is soft and coverage is not comprehensive.

3 / 5

Completeness

There is a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'SMS messages with Twilio' are natural trigger terms, but common synonyms ('text messages', 'texting') are absent and the body's OTP/Verify/IVR triggers are not surfaced, leaving common variations missing.

3 / 5

Distinctiveness Conflict Risk

'SMS messages with Twilio' is a clear niche with minimal conflict risk; only minor overlap with a broader communications skill keeps it off 5.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.