feat: improve skill scores for binance-skills-hub#188
Open
popey wants to merge 1 commit intobinance:mainfrom
Open
feat: improve skill scores for binance-skills-hub#188popey wants to merge 1 commit intobinance:mainfrom
popey wants to merge 1 commit intobinance:mainfrom
Conversation
Hullo @binance 👋 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 | |-------|--------|-------|--------| | assets | 29% | 79% | +50% | | spot | 36% | 75% | +39% | | alpha | 40% | 79% | +39% | | derivatives-trading-usds-futures | 41% | 75% | +34% | | margin-trading | 45% | 79% | +34% | | trading-signal | 75% | 83% | +8% | | square-post | 77% | 83% | +6% | | query-token-audit | 83% | 89% | +6% | | meme-rush | 83% | 83% | 0% | | crypto-market-rank | 96% | 96% | 0% | | query-address-info | 94% | 94% | 0% | | query-token-info | 94% | 94% | 0% | <details> <summary>Changes made</summary> ### binance/ skills (assets, spot, alpha, derivatives-trading-usds-futures, margin-trading) These five skills all had the same core issue: their frontmatter descriptions were extremely generic (e.g. "Binance Assets request using the Binance API") with no specific actions listed and no "Use when..." trigger guidance. This caused agents to have no idea when to select these skills. **What changed:** - Rewrote each description to list specific concrete actions (e.g. "Place spot market/limit orders, cancel orders, query order status, view trade history") - Added explicit "Use when users ask about..." clauses with natural trigger terms users would actually say - Included domain-specific keywords (e.g. "perpetual contracts", "leverage", "cross margin", "isolated margin") for better skill selection ### trading-signal - Expanded trigger terms to include "whale tracking", "wallet monitoring", "crypto signals", "on-chain analysis" - Removed duplicate curl examples (were listed both inline and in a separate "Example Requests" section) ### square-post - Expanded description with additional trigger terms ("share on Binance", "publish trading updates", "share market analysis") - Added content optimization and error handling as explicit capabilities ### query-token-audit - Replaced vague "Result Validity" section with a clear decision tree for handling `hasResult`/`isSupported` combinations - Added explicit step-by-step guidance for each risk level ### meme-rush - Added "Common Workflows" section showing how to combine Meme Rush and Topic Rush APIs for practical trading scenarios </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 - [@popey](https://github.com/popey) - 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.
Hullo @binance 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements.Here's the full before/after in text form:
Changes made
binance/ skills (assets, spot, alpha, derivatives-trading-usds-futures, margin-trading)
These five skills all had the same core issue: their frontmatter descriptions were extremely generic (e.g. "Binance Assets request using the Binance API") with no specific actions listed and no "Use when..." trigger guidance. This caused agents to have no idea when to select these skills.
What changed:
trading-signal
square-post
query-token-audit
hasResult/isSupportedcombinationsmeme-rush
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 - @popey - if you hit any snags.
Thanks in advance 🙏