mexc-futures

MEXC Futures trading with DB tracking (No KYC)

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/mexc-futures/SKILL.md

Quality

Discovery

22%

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 description is too terse and lacks the detail needed for effective skill selection. It names a domain (MEXC futures) and a feature (DB tracking) but fails to specify concrete actions or provide any guidance on when Claude should use this skill. The '(No KYC)' parenthetical is informational but doesn't help with skill selection.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions MEXC, crypto futures trading, derivatives positions, or tracking trading history'

List specific concrete actions such as 'Place futures orders, monitor open positions, track profit/loss in database, view trading history'

Expand trigger terms to include variations users might say: 'crypto futures', 'leverage trading', 'perpetual contracts', 'trading bot', 'position tracking'

Dimension	Reasoning	Score
Specificity	The description only names a domain ('MEXC Futures trading') and mentions 'DB tracking' but provides no concrete actions like 'place orders', 'monitor positions', 'track P&L', etc. The '(No KYC)' is a feature note, not an action.	1 / 3
Completeness	The description weakly addresses 'what' (futures trading with DB tracking) but completely lacks any 'when' guidance or 'Use when...' clause. There are no explicit triggers for when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains some relevant keywords ('MEXC', 'Futures', 'trading', 'DB tracking') that users might say, but misses common variations like 'crypto futures', 'derivatives', 'positions', 'orders', or 'database'.	2 / 3
Distinctiveness Conflict Risk	'MEXC' is a specific exchange which helps distinctiveness, but 'Futures trading' and 'DB tracking' are generic enough to potentially overlap with other trading or database skills. The combination provides some niche but lacks clear boundaries.	2 / 3
	Total	6 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, concise skill that provides clear command syntax for MEXC futures trading. The command reference tables are excellent and the examples are immediately usable. The main weakness is the lack of validation/verification guidance for trading operations - users should know how to confirm positions opened correctly and handle errors in high-stakes financial operations.

Suggestions

Add a brief workflow section showing: open position -> verify with /mx positions -> monitor -> close, with guidance on what to check after each trade

Include error handling guidance: what to do if a position fails to open, how to verify order fills, checking for partial fills

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. No unnecessary explanations of what futures trading is or how APIs work. Every line provides actionable information - commands, syntax, or essential notes.	3 / 3
Actionability	Fully concrete with copy-paste ready commands. Clear syntax patterns with examples showing exact usage including parameters like leverage notation (10x, 20x). Environment variable setup is explicit.	3 / 3
Workflow Clarity	Commands are clearly listed but lacks validation checkpoints for risky trading operations. No guidance on verifying position opened correctly, checking order fills, or error recovery for failed trades. For financial operations with leverage, feedback loops would be important.	2 / 3
Progressive Disclosure	Well-organized with clear sections (Quick Start, Commands by category, Examples, Notes). For a skill of this size (~70 lines), the structure is appropriate with logical grouping. No need for external file references given the scope.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: 2a8c94e

Reviewed: 29 days ago

Table of Contents

Discovery Implementation Validation

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.