feat: improve email-best-practices skill score#5
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @dandigangi 👋 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 | |-------|--------|-------|--------| | postmark-email-best-practices | 79% | 94% | +15% | | postmark | 84% | 84% | — | | postmark-send-email | 89% | 89% | — | | postmark-inbound | 90% | 90% | — | | postmark-templates | 89% | 89% | — | | postmark-webhooks | 85% | 85% | — | I focused on `postmark-email-best-practices` — it had the most room to grow (79% baseline, lowest in the repo) while the other skills were already in great shape. <details> <summary>Changes made</summary> - **Description**: Replaced topic-area phrasing with concrete action verbs (setting up SPF/DKIM/DMARC, diagnosing deliverability, implementing unsubscribe flows, etc.) so agent routers match it more precisely - **Domain authentication workflow**: Added a step-by-step setup sequence with actual DNS records (SPF TXT, DKIM CNAME, DMARC TXT) and an explicit verification checkpoint before production sends - **Inline code example**: Added a copy-paste-ready idempotent send function in the Sending Reliability section — the only section that had no executable example - **Trimmed marketing language**: Removed the "billions of emails over 15+ years" opener — agents don't need to be sold on the platform - **Reduced Notes redundancy**: Consolidated the Notes section to only the two highest-signal points that weren't already covered in the body </details> I also stress-tested your `postmark-inbound` skill against a few real-world task evals and it held up really well on MailboxHash routing for multi-tenant inbound email parsing. Kudos for that. 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 — [@yogesh-tessl](https://github.com/yogesh-tessl) — if you hit any snags. Thanks in advance 🙏
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
1 participant
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 @dandigangi 👋
I ran your skills through
tessl skill reviewat work and found targeted improvements in your skill. Here's the before/after:I focused on
postmark-email-best-practices. It had the most room to grow (79% baseline, lowest in the repo) while the other skills were already in great shape.Changes made
I also stress-tested your
postmark-inboundskill against a few real-world task evals and it held up really well on MailboxHash routing for multi-tenant inbound email parsing. Kudos for that.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 - @yogesh-tessl - if you hit any snags.
Thanks in advance 🙏