feat: improve use-notify skill score (85% → 95%)#16
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey 👋 @mic1on 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 | |-------|--------|-------|--------| | use-notify | 85% | 95% | +10% | <details> <summary>Changes made</summary> - **Description specificity**: Expanded from generic "integrate and troubleshoot" to concrete actions — "configure notification channels, set up retry policies, debug publish errors, customize @notify decorators" - **Trigger term coverage**: Added `useNotify.from_settings` and `set_default_notify_instance` as additional trigger keywords - **Inline code examples**: Added two copy-pasteable Quick Examples (decorator pattern + publisher pattern) directly in the skill body so Claude has runnable code without needing to read reference files - **Workflow verification step**: Added step 5 to the workflow — verify error handling covers `NotificationPublishError` for multi-channel failures and retry configuration </details> 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
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 👋 @mic1on
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Changes made
useNotify.from_settingsandset_default_notify_instanceas additional trigger keywordsNotificationPublishErrorfor multi-channel failures and retry configurationHonest 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 🙏