feat: improve skill scores for ai-marketing-claude - #3
Open
rohan-tessl wants to merge 1 commit into
Open
Conversation
Hey @zubair-trabzada 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the full before/after:  | Skill | Before | After | Change | |-------|--------|-------|--------| | market-seo | 46% | 89% | +43 | | market-proposal | 46% | 89% | +43 | | market-funnel | 48% | 89% | +41 | | market-brand | 43% | 84% | +41 | | market | 45% | 85% | +40 | | market-audit | 55% | 89% | +34 | | market-landing | 59% | 89% | +30 | | market-social | 59% | 89% | +30 | | market-ads | 60% | 89% | +29 | | market-launch | 61% | 89% | +28 | | market-report-pdf | 64% | 89% | +25 | | market-competitors | 60% | 81% | +21 | | market-copy | 69% | 89% | +20 | | market-report | 69% | 89% | +20 | | market-emails | 73% | 89% | +16 | **Average: 57% → 88% (+31)** <details> <summary>Changes made</summary> ### All 15 skills - **Added YAML frontmatter** — none of the skills had frontmatter (`name`, `description`), which caused them to fail validation entirely (scoring 0% without it). After adding frontmatter with proper kebab-case names and quoted descriptions, the LLM judge could actually evaluate the content. - **Added "Use when..." clauses** — every description now includes explicit trigger guidance so agents know when to select each skill, which was the single biggest scoring improvement across the board. - **Expanded trigger terms** — added natural user language variations (e.g., "GTM" for market-launch, "cart abandonment" for market-funnel, platform names for market-ads/market-social). ### High-impact content improvements - **market-brand** (43→84): Reduced from 477 to 180 lines (62%). Removed verbose tone signal tables and archetype descriptions Claude already knows. Added validation checkpoint for source material sufficiency. - **market-seo** (46→89): Reduced from 488 to 128 lines (74%). Removed basic SEO concept explanations. Added script execution validation steps. - **market-proposal** (46→89): Reduced from 387 to 158 lines (59%). Removed pricing psychology tips, follow-up sequences, and formatting guidance. Added input validation checkpoint. - **market-funnel** (48→89): Reduced from 449 to 291 lines (35%). Removed funnel type reference tables and drop-off cause matrices. Added WebFetch example and validation checkpoints. - **market** (45→85): Added concrete WebFetch example, replaced Business Context Detection section with Subagent Validation Checkpoints. ### Moderate content improvements - **market-ads** (60→89): Removed ROAS/CPA benchmark tables, condensed ad copy angle templates. - **market-copy** (69→89): Removed CTA Color Psychology section, condensed page-specific copy structures. - **market-launch** (61→89): Removed Common Launch Mistakes and Key Principles sections. - **market-social** (59→89): Removed platform demographics tables, added brand voice validation checkpoint. - **market-landing** (59→89): Condensed benchmark tables, hero scoring rubrics, and A/B test examples. - **market-competitors** (60→81): Condensed discovery methods and template tables. - **market-audit** (55→89): Condensed business type detection to bullet list format. ### Lighter touch (description-only improvements) - **market-emails** (73→89): Removed basic concept explanations and "Why It Matters" column. - **market-report** (69→89): Removed E-E-A-T explanation and glossary section. - **market-report-pdf** (64→89): Removed PDF vs Markdown comparison table and color scheme tables. </details> > **Note:** All skills originally scored 0% because they lacked YAML frontmatter. I added frontmatter with proper names and descriptions to unblock the LLM judge, then re-scored to get meaningful baselines. The "before" scores in the table above reflect those post-frontmatter baselines — the true starting point was 0% across the board. Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute. Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me - [@rohan-tessl](https://github.com/rohan-tessl) - if you hit any snags. Thanks in advance 🙏
daya-travel
pushed a commit
to daya-travel/ai-marketing-claude
that referenced
this pull request
Jun 28, 2026
… block, design-system compliant)
daya-travel
pushed a commit
to daya-travel/ai-marketing-claude
that referenced
this pull request
Jul 12, 2026
…fonts in carousel builder 4-photo variant (cover, baths, view, endcard; tips on cream cards). build-carousel.mjs switched from Google Fonts link to local FONT_CSS (proxy blocks font loading in headless Chrome). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VGyuTGrbbTkEG5Wj9ZwDpQ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey @zubair-trabzada 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements.Here's the full before/after:
Average: 57% → 88% (+31)
Changes made
All 15 skills
name,description), which caused them to fail validation entirely (scoring 0% without it). After adding frontmatter with proper kebab-case names and quoted descriptions, the LLM judge could actually evaluate the content.High-impact content improvements
Moderate content improvements
Lighter touch (description-only improvements)
Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.
Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide and ask it to optimize your skill. Ping me - @rohan-tessl - if you hit any snags.
Thanks in advance 🙏