SkillAgentSearch skills...

mt5-robot-tester

Select the best MetaTrader 5 trading robots (Expert Advisors) that have not been backtested yet, by running the MT5 Strategy Tester from the command line through a 3-round pipeline

Install / Use

npx skills add tradermonty/claude-trading-skills --skill mt5-robot-tester

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of mt5-robot-tester

mt5-robot-tester scores 93/100 on our quality scale, 665th of 2,780 Automation skills we index (top 24%).

Its SKILL.md is 8.3 KB long, well organised into 20 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

With 2,885 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so mt5-robot-tester is actively maintained.
  • Our last check on 2026-10-04 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

mt5-robot-tester compared with similar skills

All 4 of these similar skills score higher than mt5-robot-tester; compare them before choosing.

SkillScoreStarsUpdatedFormat
mt5-robot-tester (this skill)by tradermonty932.9k53d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install mt5-robot-tester?
Run npx skills add tradermonty/claude-trading-skills --skill mt5-robot-tester. The install tabs above show the steps for each supported agent.
Which AI agents does mt5-robot-tester work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is mt5-robot-tester safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is mt5-robot-tester still maintained?
The repository was last updated about 2 months ago, so mt5-robot-tester is actively maintained.

name: mt5-robot-tester description: Select the best MetaTrader 5 trading robots (Expert Advisors) that have not been backtested yet, by running the MT5 Strategy Tester from the command line through a 3-round pipeline. Use when the user wants to batch-test MT5 bots/EAs, screen robots across all symbols, optimize EA parameters, or move candidate bots to finalists based on profit, drawdown, positive months/years and equity-curve criteria. Runs terminal64.exe headless; Windows + MetaTrader 5 required at run time.

MT5 Robot Tester

Overview

Select the best MetaTrader 5 robots (Expert Advisors) from a candidates folder by driving the Strategy Tester from the command line through a 3-round pipeline, moving each bot between folders as it advances, and learning across runs to improve selection each loop. The whole run is checkpointed and resumable.

  • Round 1 — screening (all pairs): backtest the EA on each symbol in the configured common.symbols list (one Optimization=0 backtest per symbol — MT5 build 6061 leaves the Optimization=3 XML empty, so per-symbol backtests are used). Gate: ≥5 symbols profitable AND best symbol ≥3× deposit.
  • Round 2 — best-pair backtest: single backtest on the best symbol; analyze net profit %, worst drawdown %, % positive months, all-years-positive, LR Correlation, months-to-new-high.
  • Round 3 — sequential parameter optimization: optimize the 5–6 inputs after MagicNumber, one at a time, range ±50% step 5%; then a final backtest.
  • Finalist: optimized result improves on Round 2 and profit ≥4× deposit and worst drawdown ≤12%.

Tested bots move to in-testing; finalists are also copied to finalists with their optimized .set.

When to Use

  • "Prueba robots / bots / EAs en MetaTrader 5."
  • Screen a folder of MT5 Expert Advisors and pick the best across all pairs.
  • Optimize EA parameters and decide finalists by profit/drawdown/consistency.
  • Resume an interrupted testing run.

Prerequisites

  • Windows + MetaTrader 5 installed (the tester runs terminal64.exe).
  • Broker tick data downloaded (default modeling is real ticks, Model=4).
  • The three folders under MQL5\Experts: candidates, in-testing, finalists.
  • common.symbols set in the config — the pairs Round 1 backtests (your Market Watch symbols).
  • Optional per-bot .set files (config sets_dir) for the Round-2 baseline and Round-3 parameter optimization. Every input is fixed during optimization except the one parameter currently being searched; without a .set, Round 3 is skipped and the verdict comes from Round 2.
  • Close MetaTrader 5 before running — the tester needs exclusive use of the data folder.
  • Python 3.9+ (standard library only). No paid API.

Workflow

Step 1 — Configure

Copy assets/pipeline_config.template.json, fill in the three folder paths and (optionally) terminal_path. Never commit real personal paths — pass the config at run time. Defaults already encode the agreed settings (2020.01.01→2026.06.30, H1, Model=4, 10000 USD, 1:100, gates and thresholds).

Step 2 — Dry-run (optional)

Verify the generated Round-1 INIs without launching MT5:

python3 skills/mt5-robot-tester/scripts/mt5_batch_tester.py \
  --config my_config.json --output-dir reports/mt5_pipeline --dry-run

Step 3 — Run the pipeline

python3 skills/mt5-robot-tester/scripts/mt5_batch_tester.py \
  --config my_config.json --output-dir reports/mt5_pipeline

Each bot flows R1 → R2 → R3 → finalist decision. Progress is written to state.json and run.log after every step.

Step 4 — Resume if interrupted

python3 skills/mt5-robot-tester/scripts/mt5_batch_tester.py \
  --config my_config.json --output-dir reports/mt5_pipeline --resume

--resume skips completed bots and reuses finished rounds only while the execution config, EA binary, and input .set fingerprints still match. A changed period, symbol list, binary, or .set restarts that bot safely.

Optional — HTML control panel

Launch a local dashboard to see the bots in each folder, each bot's phase and verdict, and a Launch button — no CLI needed after starting it:

python3 skills/mt5-robot-tester/scripts/dashboard.py \
  --config my_config.json --output-dir reports/mt5_pipeline

It serves http://127.0.0.1:8765/ (opens automatically, localhost only). The page auto-refreshes every 3 s: folder contents, per-bot phase (R1/R2/R3/done), pass/fail verdicts, summary counts, and the live run.log. Start/stop requests are limited to the exact local origin and require the per-server CSRF token.

Step 5 — Read the results

  • leaderboard_<ts>.md / .json — ranking with verdict and key metrics.
  • learnings.json / learnings.md — what the skill learned this loop (parameter impact and symbol priors) under the configured output directory.
  • mt5_reports/ and mt5_ini/ — raw MT5 reports and configs per bot/round.

Round details

Round 1 gate (both required)

  1. count_positive_profit(passes) ≥ round1_min_positive (default 5).
  2. best_symbol_profit ≥ round1_min_profit_multiple × deposit (default 3×).

Fail → bot rejected (moved to in-testing).

Round 2 quality profile (reference thresholds)

Net profit ≥300%, worst DD <15% (larger of balance/equity %), positive months

70%, all years positive, LR Correlation ≥0.80, months-to-new-high ≤3. Reported per bot; the hard finalist gate is Round 3.

Round 3 sequential optimization

For each of the 5–6 inputs after MagicNumber (learned order first), optimize that single parameter over [V×0.5, V×1.5] step V×0.05 (Optimization=1) while fixing every other .set input, fix its best value, then continue. Run a final backtest with the exact complete input set saved for a finalist.

Finalist

evaluate_finalist: improved on Round 2 and profit ≥4× deposit and worst DD ≤12%. → copied to finalists with <bot>.set.

Self-learning across loops

learnings.json accumulates, per run: parameter average profit improvement (reorders Round-3 optimization so the most impactful parameters are tried first), symbol priors (how often each is a best pair), and per-bot verdicts. This makes selection converge faster each loop. Deterministic — plain aggregate statistics.

Output Format

  • leaderboard_<ts>.json — list of {name, verdict, best_symbol, r2_profit, final_profit, final_dd_pct, lr, reason} sorted finalists-first by profit.
  • leaderboard_<ts>.md — same as a table.
  • state.json — resumable per-bot/per-round checkpoint.

Resources

  • scripts/mt5_batch_tester.py — pipeline orchestrator + INI builders (CLI).
  • scripts/parse_mt5_optimization.py — optimization report (XML/HTML) parser + Round-1 gate.
  • scripts/parse_mt5_report.py — backtest report parser + balance-series metrics.
  • scripts/mt5_learnings.py — cross-run learning store.
  • scripts/mt5_common.py — shared parsing helpers (EN/ES headers, numbers).
  • references/mt5-cli-reference.md — MT5 [Tester]/[TesterInputs] keys, enums, report formats and caveats.
  • assets/pipeline_config.template.json — config template with placeholders.

Key Principles

  1. Never commit personal paths — folders/terminal come from config/ENV/args.
  2. Relative Report= names because build 6061 ignores absolute report paths; collect completed reports from the terminal data directory.
  3. Real ticks (Model=4) need broker tick data; it is slow — expect long runs.
  4. Resumable: every round checkpoints; --resume reuses only fingerprint- matching work and retries execution errors.
  5. Fail closed: incomplete, timed-out, stale, or unparsable reports never reject, promote, or move a candidate. Every unique Round-1 symbol must finish.
  6. Single MT5 owner: an OS lock is held for the process lifetime for each shared MT5 data folder. If child termination cannot be confirmed, the whole run stops and writes a .blocked marker; verify the recorded PID/process tree has exited before removing that marker manually.
  7. Full-period metrics: months without deals at the start, end, or across a full year remain part of the configured test period.
  8. Learn each loop: parameter/symbol statistics bias future runs toward wins.
  9. Verify against your build: report layout (esp. the deals table) and the 32 ms delay mapping can differ — see the reference's (verify) notes.

Related Skills

View on GitHub
GitHub Stars2.9k
CategoryAutomation
Updated1mo ago
Forks655

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions