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

68%

Does it follow best practices?

Impact

92%

1.55x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./creative-skills/multi-channel-ad-ideation/channels/sms/SKILL.md

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 highly actionable, well-structured instructional skill whose body is bloated by inline HTML card markup and unneeded channel statistics. Fixing the dangling external reference and moving boilerplate templates into a real bundle file would lift both conciseness and organization.

Suggestions

Move the two full inline-CSS HTML card examples into a references/ file (e.g., references/card-templates.md within this skill) and keep only a compact format summary in SKILL.md, which also fixes the currently dangling `../references/card-templates.md` path.

Trim the 'SMS Channel Advantage' statistics section (open rates, read times) that Claude doesn't need to produce good output.

Add an explicit validation step to the workflow, e.g., 'Before presenting, confirm each message plus opt-out fits within 160 (single) or 300 (multi-part) characters.'

Dimension	Reasoning	Score
Conciseness	Section-level guidance is tight, but the file carries significant padding: roughly 120 lines of inline-CSS HTML card markup for the two examples, and channel statistics Claude does not need ("98% open rate vs. 20% for email", "Read within 3 minutes on average"). Not a 2 because most sections (formulas, techniques, pitfalls) are efficient and free of concept explanations.	3 / 5
Actionability	Fully executable guidance throughout: message formulas ([Hook] + [Offer] + [CTA] + [Link] + [Opt-out]), copy-paste-ready B2C and B2B message examples, specific merge tags, concrete CTA phrasing, exact send-time windows, compliance wording, and complete HTML card templates. Examples cover the common cases.	5 / 5
Workflow Clarity	The two-phase process is clearly sequenced with an explicit checkpoint ("ONLY generate ASCII previews AFTER user confirms text concepts"), and both standalone and delegated invocation modes are defined. Not a 5 because there is no explicit step instructing Claude to verify generated messages fit the stated character limits before presenting them.	4 / 5
Progressive Disclosure	Sections are well organized, but the only external reference — `../references/card-templates.md` — points outside the skill directory and no references/ files exist in the bundle, so the link is unverifiable/broken. Meanwhile ~120 lines of card-template markup are inlined that would fit a references file. Not a 2 because structure and navigation within the body itself are good.	3 / 5
	Total	15 / 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.

A concrete, domain-specific description with good keyword coverage, weakened by the complete absence of 'when to use' trigger guidance and by capability mentions that read as feature lists rather than actions. Adding an explicit 'Use when...' clause would move it into the top tier.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks for SMS ad concepts, text message copy, or mobile campaign ideas."

Include natural synonyms such as "text message" or "text blast" so the description matches how users actually phrase the request.

Restate the feature mentions as parallel concrete actions (e.g., "Personalize messages with merge tags, optimize CTAs for mobile taps, and recommend send times") for stronger specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete primary action ("Generate SMS advertising concepts with ultra-concise mobile messaging") plus several enumerated capabilities ("personalization, CTA optimization, and timing recommendations"). It stops short of a 5 because the additional items are feature mentions rather than multiple parallel concrete actions.	4 / 5
Completeness	The 'what' is clear and specific (generate ultra-concise SMS ad concepts under 160-character constraints), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 2 because the 'what' half is concrete rather than vague.	3 / 5
Trigger Term Quality	Good natural-keyword coverage: "SMS", "advertising", "mobile messaging", "CTA", "personalization", and "timing" are phrases users would say. Not a 5 because common synonyms like "text message", "texting", or "text blast" are absent; not a 3 because coverage goes well beyond a couple of generic terms.	4 / 5
Distinctiveness Conflict Risk	"SMS advertising concepts" carves out a clear channel niche with distinct triggers, but the description does nothing to distinguish it from sibling ad-ideation skills (e.g., multi-channel or email variants referenced in the body), leaving minor overlap risk. Not a 3 since the channel constraint makes confusion with generic copywriting skills unlikely.	4 / 5
	Total	15 / 20 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
Path: creative-skills/multi-channel-ad-ideation/channels/sms/SKILL.md
Commit: 1a0845f

Reviewed: 6 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.