CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/sms-test-author

Build-an-X for SMS-flow tests - uses Twilio Magic Numbers (`+15005550006` valid recipient, `+15005550001` invalid number, `+15005550002` cannot route, `+15005550003` international restriction, etc.) and Test Credentials for safe assertion-only Twilio interactions; covers segment-counting (GSM-7 vs UCS-2 encoding); rate-limit + opt-out keyword (STOP / HELP / UNSUBSCRIBE) handling; alphanumeric sender vs short-code vs 10DLC differences. Use when authoring tests for any Twilio-backed SMS flow.

67

Quality

84%

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

Overview
Quality
Evals
Security
Files

Quality

Content

71%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 well-structured, actionable testing skill with concrete code and a clear step sequence plus an end-to-end checklist. The main weakness is progressive disclosure: all reference tables are inlined in one ~250-line file with no bundle files to offload the lookup data.

Suggestions

Move the Magic Numbers table and the opt-out keyword / sender-type comparison tables into a references/ file (e.g. references/magic-numbers.md) and link to it from the body, keeping SKILL.md as an overview.

Define or stub the helper functions used in examples (twilio_test_client(), calculate_segments(), capture_sms_send()) so the code is fully copy-paste executable.

Tighten the Overview by dropping the 'dominant SMS provider for B2B SaaS' framing line, which states general knowledge rather than skill-specific guidance.

DimensionReasoningScore

Conciseness

Mostly lean, domain-specific content (Magic Numbers, GSM-7/UCS-2 segment limits, CTIA keywords, sender-type matrices) with only minor framing padding like 'Twilio is the dominant SMS provider for B2B SaaS' that could be trimmed.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready pytest examples for each path (happy path, invalid number, segments, rate limit, STOP webhook, sender type), with only minor gaps where helper stubs like twilio_test_client() and calculate_segments() are used without definition.

4 / 5

Workflow Clarity

A clear 9-step sequence capped by an 'End-to-end test recipe' checklist, with test assertions acting as validation checkpoints; not a destructive/batch operation so no hard cap applies, though explicit validate→fix→retry loops are not spelled out.

4 / 5

Progressive Disclosure

No bundle files exist, yet the ~250-line body inlines substantial reference data (full Magic Numbers table, opt-out keyword table, sender-type comparison) that could live in a separate reference file; external doc URLs and sister-skill links are signaled but the single-file structure is heavier than the well-organized-segments exception allows.

3 / 5

Total

15

/

20

Passed

Description

92%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 dense, specific description that concretely enumerates capabilities and gives an explicit 'Use when' trigger with minimal conflict risk. The only minor gap is a few natural synonyms (text message, MMS) among the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities with domain detail — 'Twilio Magic Numbers', 'Test Credentials for safe assertion-only Twilio interactions', 'segment-counting (GSM-7 vs UCS-2 encoding)', 'rate-limit + opt-out keyword (STOP / HELP / UNSUBSCRIBE) handling', 'alphanumeric sender vs short-code vs 10DLC differences' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (the enumerated testing capabilities) and when ('Use when authoring tests for any Twilio-backed SMS flow.'), matching the anchor that requires concrete trigger phrases for both.

5 / 5

Trigger Term Quality

Strong natural keywords (SMS-flow tests, Twilio, segment-counting, opt-out, STOP/HELP/UNSUBSCRIBE, rate-limit, 10DLC, short-code) but a few common user phrasings like 'text message' or 'MMS' are absent, so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — Twilio-backed SMS test authoring with Magic Numbers and segment/opt-out/sender-type concerns — with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

19

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents