square-post
Post content to Binance Square (Binance social platform for sharing trading insights). Auto-run on messages like 'post to square', 'square post'. Supports pure text posts.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/binance/square-post/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a reasonably well-crafted description that clearly identifies its niche (Binance Square posting) and provides explicit trigger terms. Its main weakness is limited specificity in capabilities — it only mentions pure text posts without detailing other potential features. The description is concise and uses appropriate third-person voice.
Suggestions
Expand the capabilities list to mention other supported actions or content types (e.g., image posts, hashtags, draft management) if applicable, to improve specificity.
Consider adding more natural trigger variations such as 'share on Binance', 'publish to square', or 'Binance post' to broaden keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Binance Square) and a specific action (post content, supports pure text posts), but the range of actions is limited — only text posting is mentioned with no other capabilities like editing, scheduling, or analytics. | 2 / 3 |
Completeness | Clearly answers 'what' (post content to Binance Square, supports pure text posts) and 'when' (auto-run on messages like 'post to square', 'square post'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'post to square', 'square post', and mentions 'Binance Square' and 'trading insights'. These are realistic terms a user would use when wanting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — Binance Square is a specific platform, and the trigger terms ('post to square', 'square post') are unlikely to conflict with other skills. The description clearly carves out a unique domain. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable API skill with a complete curl example, thorough error codes, and clear agent behavior guidelines. Its main weaknesses are some redundancy (authentication headers repeated), and the workflow could benefit from explicit error recovery loops (e.g., retry on network error 10004, prompt user on sensitive word detection). The security guidance around key masking is a nice touch.
Suggestions
Remove the duplicate 'Authentication' section since the required header is already documented in the API section's Request Headers table.
Add explicit error recovery guidance in the Agent Behavior section, e.g., 'If error 10004 (network error), retry up to 2 times; if 20002/20022 (sensitive words), inform user and ask them to revise content.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but has some redundancy — the authentication section repeats the header table already shown in the API section, and the request headers are listed twice. The error handling table is comprehensive but could be more compact. Some sections like 'Notes' add little value. | 2 / 3 |
Actionability | Provides a fully executable curl example, complete API endpoint, exact headers, request/response schemas, post URL construction format, and a comprehensive error code table. Claude can directly use this to make API calls. | 3 / 3 |
Workflow Clarity | The Agent Behavior section outlines a clear sequence (check key → prompt for content → optimize → post → return URL), but lacks explicit validation checkpoints and error recovery loops. Step 8 handles a specific edge case, but there's no general 'if API returns error code X, do Y' feedback loop for the posting operation itself. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but everything is in a single file with no bundle files for reference. The error code table and security guidelines could potentially be separated, though for a skill of this size (~120 lines) it's borderline acceptable. The structure is reasonable but slightly monolithic. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- binance/binance-skills-hub
- Commit
68fcfa1
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.