CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mexc-futures

MEXC Futures trading with DB tracking (No KYC)

57

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/mexc-futures/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%Weight 40%Scale 1-5

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

The body is lean and actionable with well-organized command reference tables, but workflows involving destructive leveraged trading lack validation or confirmation checkpoints, capping workflow clarity. Adding safety/verification steps would raise the score.

Suggestions

Add an explicit confirmation or validation step before destructive/batch operations such as '/mx closeall' and high-leverage opens (e.g., 'Confirm position size and leverage before submitting; verify with /mx positions afterward').

Clarify the credential setup workflow with a concrete sequence (set env vars -> verify auth via '/mx balance' -> only then trade) rather than implying it through a quick-start snippet.

DimensionReasoningScore

Conciseness

Lean tables and examples with no padding or explanation of concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Provides concrete, executable command syntax with worked examples, but the authentication/setup flow is only implied via env vars with minor gaps.

4 / 5

Workflow Clarity

Commands are well organized but destructive/batch operations (closeall, leveraged opens) lack validation or confirmation checkpoints; the destructive-skill cap applies.

3 / 5

Progressive Disclosure

Under 50 lines with no external references needed; sections are cleanly organized into Quick Start, command categories, Examples, and Notes, satisfying the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 is concise and domain-specific but lacks a 'Use when...' trigger clause, which caps completeness, and omits natural keyword variations. It is distinguishable but would benefit from explicit invocation guidance.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user wants to trade perpetual futures on MEXC or check trade history from the database').

Include natural user-facing trigger phrases or synonyms such as 'perpetuals', 'crypto leverage trading', or 'MEXC positions' alongside the technical terms.

DimensionReasoningScore

Specificity

Names the domain ('MEXC Futures trading') and one-to-two concrete actions ('trading', 'DB tracking'), but coverage is not comprehensive.

3 / 5

Completeness

States clearly what the skill does but provides no 'Use when...' trigger clause; per guidelines a missing trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant niche terms ('MEXC Futures', 'DB tracking', 'No KYC') but lacks natural synonyms or common variations a user might phrase.

3 / 5

Distinctiveness Conflict Risk

Niche-specific phrasing (MEXC Futures, No KYC) makes it mostly distinct with only minor overlap risk against other trading skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/mexc-futures/SKILL.md

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.