CtrlK
BlogDocsLog inGet started
Tessl Logo

send-sms-textbelt

Send SMS text messages to phone numbers. Use when the user asks to send a text, send an SMS, text someone, message a phone number, or send a notification via text message.

71

Quality

87%

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

85%

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

The content is concise, well-organized, and provides a clear sequenced workflow with a verification checkpoint, appropriate for a simple single-purpose skill. The main defect is the malformed JSON payload in the Step 2 curl example, which prevents it from being fully executable.

Suggestions

Fix the Step 2 curl `-d` payload so the JSON is valid and complete — include "api", "path", "phone", and "message" inside a single properly-closed JSON object so the command is executable as written.

Clarify how the {textId} placeholder in the status endpoint is substituted (e.g., show it interpolated into the `path` value in the request body) to make the verification step unambiguous.

Consider noting that the `/status` call still requires the phone/message-free request body shape, so the status curl example mirrors the correct payload structure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it provides commands, endpoint shapes, and constraints without padding with concepts Claude already knows, so every section earns its place.

3 / 3

Actionability

The curl commands are concrete and mostly copy-paste ready, but the Step 2 `-d` JSON payload is malformed (the object closes prematurely with `}'` and the "phone"/"message" fields sit outside the JSON), so the example is not fully executable as written.

2 / 3

Workflow Clarity

The three-step workflow is clearly sequenced and includes an explicit verification checkpoint (Step 3 uses the returned `textId` to check delivery status), matching the score-3 anchor with a validation/feedback loop.

3 / 3

Progressive Disclosure

This is a simple, single-purpose skill under 50 lines with no bundle files and well-organized sections (Setup, Workflow, Response, Constraints, Error Handling), which per the simple-skills scoring note earns a 3 on progressive disclosure.

3 / 3

Total

11

/

12

Passed

Description

90%

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 concise and well-structured, clearly answering both what the skill does and when to use it with a strong set of natural trigger terms. The only gap is that it names a single capability rather than enumerating multiple concrete actions.

DimensionReasoningScore

Specificity

"Send SMS text messages to phone numbers" names the domain and one concrete action, but it lists only a single action rather than multiple specific capabilities, matching the score-2 anchor rather than the multi-action score-3 example.

2 / 3

Completeness

It explicitly answers both what ("Send SMS text messages to phone numbers") and when ("Use when the user asks to..."), matching the score-3 anchor that requires explicit triggers alongside the capability statement.

3 / 3

Trigger Term Quality

It covers natural variations users would actually say — "send a text, send an SMS, text someone, message a phone number, or send a notification via text message" — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

The SMS/text-messaging niche is clearly delimited with distinct triggers, making it unlikely to fire for unrelated skills and matching the score-3 anchor for a clear niche.

3 / 3

Total

11

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-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.