CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-sms

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

66

Quality

80%

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 ./skills/twilio-sms/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 an exemplary lean, command-first reference with fully executable snippets and a clear numbered credential workflow with an auth verification checkpoint. The only gap is the absence of an explicit validate/recover feedback loop around the destructive buy and delete operations.

Suggestions

Add an explicit feedback loop for purchases (e.g. after buying, verify capabilities.sms is true and the number appears in the list before reporting success; if it fails, surface the Twilio error and retry criteria).

Make the retention/release rule actionable with the exact update/delete command and a confirmation prompt before any release, since releasing a number is destructive.

Surface a one-line verification step after `profiles:create` (e.g. re-run `profiles:list` to confirm 'default' is active) to close the CLI-setup checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and command-first: every section is a labeled action with executable curl/CLI snippets and no padding explaining what Twilio or SMS is, so every token earns its place.

5 / 5

Actionability

Guidance is fully executable and copy-paste ready across buying, listing, sending, and fetching messages, with concrete jq parsing and REST fallbacks covering the common cases.

5 / 5

Workflow Clarity

The Credential Route is a clearly numbered sequence with an explicit verification checkpoint (curl auth check before purchase/send), but the destructive buy/delete operations lack an explicit validate-and-recover feedback loop, leaving a minor validation gap.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is under 50 lines with well-organized sections (Safety, Credential Route, CLI Setup, Numbers, SMS, Notes), satisfying the simple-skill exception for a top score without external references.

5 / 5

Total

19

/

20

Passed

Description

66%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 specific and names a clear Twilio SMS niche with concrete operations, but it omits an explicit 'Use when...' trigger clause, which the rubric caps at completeness 3. Trigger-term coverage is good but lacks synonyms.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when the user asks to buy, list, or keep Twilio numbers, or to send/check SMS messages') to lift completeness above 3.

Broaden trigger terms with synonyms users say naturally, e.g. 'texts', 'SMS', 'Twilio numbers', 'phone numbers'.

Spell out 'keep' as a concrete action (e.g. 'label and retain numbers') so each verb is unambiguous.

DimensionReasoningScore

Specificity

Lists several specific concrete actions ('buy/list/keep numbers, send/check messages, credential routing') rather than vague language, though 'keep' and 'credential routing' are slightly terse and could enumerate more sub-actions for full coverage.

4 / 5

Completeness

It clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural user-facing terms like 'numbers', 'send texts', 'messages' are present and would be said by users, but it lacks common synonyms or file/extension cues and omits explicit 'SMS' as a standalone trigger word beyond the title.

4 / 5

Distinctiveness Conflict Risk

The Twilio SMS niche with number and message operations is mostly distinct with only minor overlap risk against a generic telephony or 1Password skill.

4 / 5

Total

15

/

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

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.