CtrlK
BlogDocsLog inGet started
Tessl Logo

sms

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

64

1.55x
Quality

47%

Does it follow best practices?

Impact

92%

1.55x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./creative-skills/multi-channel-ad-ideation/channels/sms/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

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 strong in specificity and distinctiveness, clearly carving out a niche around SMS advertising with concrete capabilities listed. However, it lacks an explicit 'Use when...' clause that would help Claude know when to select this skill, and it could benefit from more natural user-facing trigger terms like 'text message' or 'SMS marketing campaign'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about SMS campaigns, text message marketing, or mobile advertising copy.'

Include common user-facing synonyms and variations such as 'text message', 'texting campaign', 'SMS marketing', and 'text ads' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: generating SMS advertising concepts, optimizing for 160-character constraints, personalization, CTA optimization, and timing recommendations.

3 / 3

Completeness

Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.

2 / 3

Trigger Term Quality

Includes good terms like 'SMS', 'advertising', 'mobile messaging', '160-character', and 'CTA', but misses common user variations like 'text message', 'texting campaign', 'SMS marketing', or 'text ads'.

2 / 3

Distinctiveness Conflict Risk

The combination of SMS, 160-character constraints, and mobile messaging advertising creates a very clear niche that is unlikely to conflict with other skills like general copywriting or email marketing.

3 / 3

Total

10

/

12

Passed

Implementation

27%

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

This skill suffers primarily from extreme verbosity - it explains SMS marketing fundamentals that Claude already knows, includes massive inline HTML templates, and packs too much reference material into a single file. The actionability is moderate with useful message formulas and examples, but the lack of validation checkpoints (especially for character count verification) and the monolithic structure significantly weaken its effectiveness. The referenced card-templates.md file doesn't exist in the bundle, creating a broken reference.

Suggestions

Cut the 'SMS Channel Advantage' section entirely and trim compliance/timing sections to bullet-point essentials - Claude knows what SMS is and can infer best practices from concise rules.

Move the massive HTML card templates to a separate reference file (e.g., `references/card-templates.md`) and reference it, rather than inlining ~100 lines of HTML styling.

Add an explicit validation step in the workflow: 'After generating each concept, verify character count is ≤160 (single) or ≤300 (multi-part), includes opt-out text, and includes brand identification.'

Remove explanatory content like 'Highest open rates - 98% open rate vs. 20% for email' and 'Feels like a message from a friend' - these don't help Claude generate better SMS concepts.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~200+ lines. It explains concepts Claude already knows (what SMS open rates are, that SMS is 'direct & personal', what plain text means), includes massive inline HTML card templates that bloat the content enormously, and repeats information (character limit handling appears multiple times). The 'SMS Channel Advantage' section is entirely unnecessary context.

1 / 3

Actionability

The skill provides concrete SMS message examples and specific formulas (Hook + Offer + CTA + Link + Opt-out), which is helpful. However, there's no executable code, the card template HTML is presentational rather than functional, and the guidance is more about SMS marketing knowledge than step-by-step instructions Claude can follow to generate concepts. The phased output format is somewhat clear but lacks precision.

2 / 3

Workflow Clarity

There's a clear two-phase workflow (Phase 1: text concepts, Phase 2: ASCII previews after confirmation), and the standalone vs. delegated usage paths are described. However, there are no explicit validation checkpoints - no step to verify character counts are within limits, no verification that opt-out text is included, no feedback loop for when messages exceed 160 characters.

2 / 3

Progressive Disclosure

The skill is a monolithic wall of text with everything inline. It references `../references/card-templates.md` but no bundle files exist to support this. The massive HTML card templates should be in a separate reference file. Timing recommendations, compliance essentials, and conciseness techniques could all be split out, but instead everything is crammed into one long document.

1 / 3

Total

6

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
treasure-data/td-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.