Skip to content

feat: improve sms skill score (58% → 90%) - #182

Open
yogesh-tessl wants to merge 1 commit into
treasure-data:mainfrom
yogesh-tessl:improve/skill-review-optimization
Open

feat: improve sms skill score (58% → 90%)#182
yogesh-tessl wants to merge 1 commit into
treasure-data:mainfrom
yogesh-tessl:improve/skill-review-optimization

Conversation

@yogesh-tessl

@yogesh-tessl yogesh-tessl commented May 13, 2026

Copy link
Copy Markdown

Hey @xerial 👋

truly impressive work. 86 skills across 15 categories, from SQL optimisation to realtime personalisation to creative workflows. This is one of the most comprehensive skill collections I've come across.

ran your skills through tessl skill review at work and found some targeted improvements for the sms channel skill. Here's the before/after:

Skill Before After Change
sms 58% 90% +32%
Changes made

Description improvements (biggest impact):

  • Added explicit "Use when..." clause with natural trigger terms (SMS campaigns, text message marketing, mobile ad copy, texting promotions, SMS marketing strategy)
  • Added common synonyms like "text message" to improve skill selection accuracy

Content improvements:

  • Removed "SMS Channel Advantage" section - Claude already knows SMS open rates and delivery characteristics
  • Replaced massive inline HTML card template examples (~125 lines of styled HTML) with a reference to the existing ../references/card-templates.md - same information, vastly fewer tokens
  • Added explicit character-count validation step (Phase 2) so the agent verifies each concept fits within 160/300 char limits before presenting to the user
  • Consolidated timing recommendations into a compact markdown table
  • Streamlined compliance, CTA, and personalization sections - preserved all domain-specific guidance, removed generic marketing filler

also stress-tested your sms skill against a few real-world task evals and it held up really well on multi-part B2B personalization with {{first_name}} merge tags under the 300-character limit. Kudos for that.

quick honest disclosure. I work at https://github.com/tesslio where we build tooling around skills like these. Not a pitch, just saw room for improvement and wanted to contribute.

if you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.

Hey @xerial 👋

I ran your skills through `tessl skill review` at work and found some targeted improvements for the `sms` channel skill. Here's the before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| sms | 58% | 90% | +32% |

**Description improvements (biggest impact):**
- Added explicit "Use when..." clause with natural trigger terms
- Added common synonyms like "text message" to improve skill selection

**Content improvements:**
- Removed "SMS Channel Advantage" section (Claude already knows this)
- Replaced ~125 lines of inline HTML card templates with reference to existing card-templates.md
- Added character-count validation step (Phase 2)
- Consolidated timing into compact markdown table
- Streamlined compliance, CTA, and personalization sections

Result: 287 lines → 107 lines with cleaner three-phase workflow.
@yogesh-tessl
yogesh-tessl requested review from a team as code owners May 13, 2026 16:31
@yogesh-tessl

Copy link
Copy Markdown
Author

hey @xerial, just checking in on this one, happy to make any changes if something needs tweaking!
Take your time, totally understand if reviews follow a cadence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant