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

90%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 lean, highly actionable single-file skill: nearly every line is an executable command, workflows are sequenced with explicit auth validation checkpoints, and organization is clean. Minor room to improve: give post-purchase verification its own command and add a brief error-recovery note for failed sends.

DimensionReasoningScore

Conciseness

The body is nearly all executable commands with terse, non-obvious lead-ins ("Twilio CLI profile creation requires account auth token, not just API key creds", "Twilio CLI JSON can return an array for single-resource commands"). It explains nothing Claude already knows and every token earns its place — matches the lean/efficient 5 anchor, not 4's 'minor trimming possible'.

5 / 5

Actionability

Copy-paste-ready curl and npx -y twilio-cli commands with concrete flags cover the common cases: list, search inventory, buy, label/keep, send, fetch, inbound and outbound checks — plus a REST fallback and a jq defensive-parse snippet. Fully executable and comprehensive, matching the 5 anchor.

5 / 5

Workflow Clarity

The Credential Route is a numbered 1-6 sequence with an explicit auth checkpoint ("Verify auth before any purchase/send") and the purchase flow includes "Verify ownership/capabilities after purchase" plus a retention rule, so the destructive-operation cap does not apply. Not 5: post-purchase verification is stated without its own command and there is no error-recovery loop; not 3: checkpoints are explicit rather than missing.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is a single self-contained file with well-organized sections (Safety / Credential Route / CLI Setup / Numbers / SMS / Notes); nothing clearly belongs in a separate file. Above 3's 'could be better organized' but not a 5: at ~147 lines it exceeds the small-skill threshold where well-organized sections alone earn a 5.

4 / 5

Total

18

/

20

Passed

Description

70%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 concise, specific, and distinctive description that names concrete capabilities in the Twilio SMS domain. Its main weakness is the missing 'Use when...' trigger clause, which both caps completeness and slightly limits trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions Twilio, SMS, texting, buying or listing phone numbers, or sending/checking text messages."

Add natural synonyms users would say — "texts"/"texting" and "phone numbers" — to broaden trigger-term coverage.

Optionally mention number search/provisioning (searching available numbers) so the 'what' covers the full buy workflow.

DimensionReasoningScore

Specificity

"buy/list/keep numbers", "send/check messages", and "credential routing" are several specific concrete actions in a named domain, but coverage is terse (no number search/provisioning or inbound/outbound distinction). Fits 'lists several specific actions; minor gaps' rather than 5's comprehensive coverage or 3's 1-2 actions.

4 / 5

Completeness

The 'what' is clear and concrete (Twilio SMS CLI operations), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4, which requires both what and when present.

3 / 5

Trigger Term Quality

"Twilio SMS" plus "numbers" and "messages" give good natural keyword coverage a user would say, but common synonyms like "text"/"texting" or the spelled-out "phone numbers" are missing. Not 5 (not comprehensive including synonyms); clearly above 3's generic keyword level.

4 / 5

Distinctiveness Conflict Risk

"Twilio SMS CLI" carves out a clear niche with distinct triggers (Twilio, SMS, phone numbers, credential routing) and minimal conflict risk with other skills. Matches the 5 anchor exactly; 4 would require acknowledged overlap that isn't there.

5 / 5

Total

16

/

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.

Validation — 15 / 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.