CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-sms

Twilio SMS CLI: buy/list/keep numbers, send/check messages, credential routing.

68

Quality

83%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, executable, and well-structured, with concrete commands and explicit verification checkpoints for credential auth and post-purchase checks. There is little to improve; it assumes Claude's competence and avoids token waste.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no padding or explanation of concepts Claude already knows; every section earns its tokens. It does not fall to 2 because there is no unnecessary explanatory prose.

3 / 3

Actionability

Provides fully executable, copy-paste-ready curl and npx twilio-cli commands plus defensive jq parsing, matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

The credential route is a clear numbered sequence with an explicit validation checkpoint (step 6 'Verify auth before any purchase/send') and post-purchase capability verification, satisfying the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

Single-file skill with well-organized sections (Safety, Credential Route, CLI Setup, Numbers, SMS, Notes) and no nested external references; for a no-bundle skill with clean sectioning this matches the top anchor.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and distinct, naming concrete Twilio SMS actions and a clearly bounded niche. Its main weakness is the lack of an explicit 'Use when...' trigger clause and coverage of natural phrasings like 'texts' or 'text messages'.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when buying or listing Twilio numbers, sending or checking SMS/texts, or routing Twilio credentials').

Broaden trigger terms to include natural user phrasings such as 'texts', 'text messages', and 'phone numbers'.

Mention checking inbound/outbound messages in the description to fully mirror the body's scope.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("buy/list/keep numbers, send/check messages, credential routing") rather than vague language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes the natural keyword "Twilio SMS" but misses common variations a user would say such as "texts", "text messages", or "phone numbers", so it lands at 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

"Twilio SMS CLI" names a clear niche with distinct triggers that are unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
steipete/agent-scripts
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.