mexc-futures

MEXC Futures trading with DB tracking (No KYC)

Quality

52%

Does it follow best practices?

Impact

—

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

Content

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 clean, well-structured command reference that is concise and easy to scan. However, it lacks critical context about what tool/system implements the `/mx` commands, has no setup instructions beyond environment variables, and is missing validation/confirmation steps for financial operations. It reads more like a cheat sheet for an existing tool than a complete skill teaching Claude how to perform the task.

Suggestions

Explain what implements the `/mx` commands — is it a specific script, CLI tool, or alias? Include installation/setup instructions or reference a setup file.

Add validation checkpoints for trading workflows: e.g., after opening a position, verify with `/mx positions`; before closing all, confirm open positions first.

Include error handling guidance — what happens if a trade fails, credentials are wrong, or insufficient balance? Provide expected error outputs and recovery steps.

Reference or link to documentation for the database setup/schema since DB tracking is a core feature mentioned in the description.

Dimension	Reasoning	Score
Conciseness	Very lean and efficient. No unnecessary explanations of what futures trading is, what leverage means, or how APIs work. Every line serves a purpose — commands, examples, or essential notes.	3 / 3
Actionability	The commands are clearly listed with syntax and examples, but they reference a `/mx` command system without explaining what implements it (a script, alias, CLI tool?). There's no indication of how to set up the tool, install dependencies, or what runs behind these commands, making them not truly copy-paste executable.	2 / 3
Workflow Clarity	The quick start provides a basic sequence (set credentials → check balance → open position → view stats), but there are no validation checkpoints. Trading involves destructive/financial operations — there's no mention of confirming orders, checking position status after opening, or error handling for failed trades.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but everything is in a single file. The description mentions 'DB tracking' suggesting database setup details that could be referenced separately. There are no links to additional documentation for setup, API configuration, or the database schema.	2 / 3
	Total	9 / 12 Passed

Description

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear niche (MEXC futures trading) which makes it distinctive, but it fails to list specific actions the skill performs and entirely lacks trigger guidance for when Claude should select it. It reads more like a label than a functional description.

Suggestions

Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about placing futures trades on MEXC, checking positions, or managing orders on MEXC exchange.'

List specific concrete actions the skill performs, e.g., 'Places and manages futures orders on MEXC exchange, tracks trades and PnL in a local database, handles position sizing and leverage settings.'

Include additional natural trigger terms users might say, such as 'crypto futures', 'leverage trading', 'MEXC orders', 'perpetual contracts', or 'trading bot'.

Dimension	Reasoning	Score
Specificity	Names the domain (MEXC Futures trading) and mentions DB tracking and No KYC, but does not list specific concrete actions like placing orders, managing positions, querying balances, etc.	2 / 3
Completeness	Provides a partial 'what' (futures trading with DB tracking) but completely lacks any 'when should Claude use it' guidance. Per rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak, warranting a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'MEXC', 'Futures', 'trading', and 'No KYC' that users might naturally say, but misses common variations like 'crypto trading', 'derivatives', 'leverage', 'positions', or 'orders'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'MEXC' (a specific exchange), 'Futures trading', 'DB tracking', and 'No KYC' creates a very distinct niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 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: e71a5f6

Reviewed: 2 months 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.