mt5-log-reader

Parse MetaTrader 5 log files to validate execution and surface errors.

1|Updated Nov 2, 2025
One-click install
npx skills add https://github.com/terrylica/mql5-crossover --skill mt5-log-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mt5-log-reader
Source: https://github.com/terrylica/mql5-crossover/tree/main/.claude/skills/mt5-log-reader
Command: npx skills add https://github.com/terrylica/mql5-crossover --skill mt5-log-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reads MetaTrader 5 log files programmatically to access Print() output from indicators, scripts, and expert advisors. It supports a dual logging pattern where Print() statements go to MT5 logs for human readability and CSV files provide structured data for validation.

Core Features & Use Cases

  • Log exploration: Filter and search MT5 logs to surface relevant messages, errors, and timing.
  • Validation workflow: Correlate log output with unit tests and validation checks to confirm correct behavior.
  • Troubleshooting: Quickly diagnose issues reported in the Experts pane or runtime logs by inspecting messages and version info.

Quick Start

Provide or point to the MT5 log file (e.g., $MQL5_ROOT/Program Files/MetaTrader 5/MQL5/Logs/YYYYMMDD.log) and specify the keywords or indicators you want to investigate, for example: search for "MyIndicator" and "error" on today's log to confirm successful execution.

Frequently Asked Questions about mt5-log-reader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read and parse MT5 log files to validate indicator output?

Parse MT5 log files programmatically to extract and validate Print() output from indicators, scripts, and expert advisors. The Skill reads UTF-16LE, tab-separated logs from the MT5 Logs directory, searches for specific keywords and error patterns, and surfaces compilation or runtime errors without modifying source files.

Can I automate validation of MT5 debugging output across multiple indicators?

Yes. Automate validation by filtering MT5 logs for specific indicators, scripts, or advisors to correlate Print() statements with unit tests and validation checks. Search for keywords, version info, and debug entries to confirm correct execution across multiple components in a single workflow.

What's the best way to diagnose MT5 expert advisor errors from log files?

Extract and inspect messages, version info, and error entries directly from MT5 log files to quickly diagnose issues reported in the Experts pane or runtime logs. Pattern-based search surfaces relevant compilation and runtime errors without manual log inspection.

Does log validation work with both Print() output and CSV logging in MT5?

Yes. The Skill supports a dual logging pattern where Print() statements go to MT5 logs for human readability while CSV files provide structured data. Correlate both formats within a single validation workflow to confirm behavior across indicators and advisors.

How do I construct the correct path to today's MT5 log file?

The Skill automates path construction to today's log file in the MT5 installation directory (e.g., MQL5/Logs/YYYYMMDD.log). Specify keywords or indicator names to search the correct log without manual path lookup.

What limitations should I know about parsing MT5 log files?

The Skill reads UTF-16LE, tab-separated logs and reports results without altering source files. Logs must be accessible from the MT5 installation path; search accuracy depends on keyword specificity and log retention policies within your MT5 environment.