sms

Generate SMS advertising concepts with ultra-concise mobile messaging optimized for 160-character constraints. Includes personalization, CTA optimization, and timing recommendations.

1.55x

Quality

—

Does it follow best practices?

Impact

92%

1.55x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

The content is highly actionable with a clear phased workflow, but conciseness suffers from verbose inline HTML card examples and a dangling reference to a missing bundle file.

Suggestions

Move the inline HTML <details> concept-card examples into a separate referenced file (e.g., references/example-concepts.md) and link to it, reducing the inline markup.

Create the referenced ../references/card-templates.md file or remove/fix the dangling reference so navigation actually resolves.

Trim obvious statements and decorative markup that restate what Claude already knows about SMS to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but ~125 lines of inline HTML/CSS <details> card markup and a few obvious statements ('SMS is direct, immediate, and highly personal') pad it beyond the lean anchor.	2 / 3
Actionability	It provides copy-paste-ready message formulas, concrete example SMS texts, specific CTAs, timing windows, and compliance phrasings — fully actionable, specific guidance.	3 / 3
Workflow Clarity	The two-phase workflow is clearly sequenced with an explicit gating checkpoint ('ONLY generate ASCII previews AFTER user confirms'), plus a pitfalls/Do-this-instead checklist.	3 / 3
Progressive Disclosure	Sections are organized, but the example concept cards are a large inline HTML monolith that should be separate, and the one referenced file (../references/card-templates.md) does not exist.	2 / 3
	Total	10 / 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 occupies a clear niche, but lacks explicit 'when to use' trigger guidance and omits common natural trigger terms users would actually say.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when creating SMS ads, text message marketing, or mobile promotional copy').

Include common everyday terms users would say — 'texts', 'text messages', 'SMS marketing' — alongside the current phrasing.

Keep the concise capability list but ensure the trigger guidance names concrete user intents rather than technical constraints like '160-character constraints'.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities — 'Generate SMS advertising concepts', 'personalization, CTA optimization, and timing recommendations' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	It has relevant terms ('SMS advertising concepts', 'mobile messaging', '160-character constraints') but misses common natural variations a user would say, such as 'texts', 'text messages', or 'SMS marketing'.	2 / 3
Distinctiveness Conflict Risk	The SMS/mobile-messaging-with-160-character-constraints niche is clearly distinguishable from generic copywriting or ad-ideation skills and unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: treasure-data/td-skills
Commit: 50d5a57

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.