SKILLEMALL.ai
GitHub ↗ RU Sign in

BD mt5-http-trader

Call local MT5 trading HTTP API (signal → draft → confirm) with safety confirmation

ClawHub Agent Skills author: XuanyuShen19 v1.0.0 1 file body ≈ 538 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
78/100
safety, quality, tests
Safety 60%
100
Quality 40%
46
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected flow-seq-start at node end at line 6, column 34: metadata: { "openclaw": { "os": \["win32"], "emoji": "📈" } } ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 48/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (mt5-http-trader) differs from the folder (mt5trade)
  • 50Steps. 2 steps
  • 70Failures and branches. 5 branches
  • 100Tools and files. No external tools needed
  • 100Execution cost. Instruction body is 538 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 83: 120–800 characters recommended
  • +4Structure: 0 headings, hard to scan
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions

Quality base 70; lint remarks subtract, signals add up to 100. Result: 46.

External checks

ClawHub: suspicious
This skill is mostly coherent, but it gives an agent high-impact trade-confirmation authority through raw PowerShell commands with an unsafe JSON-pasting pattern.
LLM: suspicious (medium) · VirusTotal: suspicious · 28 May 2026