メニュー
Use when compiling MQL5 experts, indicators, scripts, or include-dependent code in this workspace from the terminal. Follow the local MetaEditor command pattern and always inspect the compilation log after running it.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Orquestar cuentas MetaTrader 5 del workspace actual usando MQL5\Scripts\interface.py, archivos accounts/account_id/info.md, accounts/account_id/bots.ini y notificaciones Telegram. Use when Codex is asked to orchestrate accounts, coordinate account-specific bots, prepare or inspect bots.ini for an MT5 account, or notify the configured Telegram chat/channel about account orchestration status.
Use the local MetaTrader 5 Python trading CLI at MQL5\Scripts\interface.py. Use when Codex needs to explain, run, validate, or troubleshoot command-line trading operations such as opening market or pending orders, setting or editing SL/TP, closing positions, canceling pending orders, listing opened trades or pending orders, reading recent trade history, or checking account and symbol details.
Analyze market regime and session structure in this MQL5 workspace using reusable CSV exports from an MQL5 script. Use when Codex needs to classify a market as Tendencial or Lateral with moving average and ATR, export per-session data to Terminal Common Files for M15, H1, and D1, and then read those CSV files directly to summarize insights and recommendations by session without recreating scripts that already exist.
Run MetaTrader 5 parameter optimizations in this workspace and summarize real results from exported optimization reports. Use when Codex needs to optimize EA inputs such as SL, TP, RSI values, or other inputs for experts under MQL5\Experts, by generating a tester .ini with [TesterInputs], launching MT5 from the terminal, and reading the resulting XML ranking.
Use when running MetaTrader 5 Strategy Tester backtests from the terminal in this workspace. Ask the user for the test configuration field by field before launching the test, using the current project defaults unless the user changes them.
Work with Forge-hosted Git repositories from this workspace, including login, staged commits, and push workflows. Use when Codex needs to prepare or send commits to Forge or Forgejo remotes such as forge.mql5.io, refresh credentials, inspect Git status, or write commit messages that follow Conventional Commits like feat(rsi): summary.
| name | compile-mql5 |
| description | Use when compiling MQL5 experts, indicators, scripts, or include-dependent code in this workspace from the terminal. Follow the local MetaEditor command pattern and always inspect the compilation log after running it. |
Use this skill when compiling .mq5 files in this repository.
Use MetaEditor64.exe from the local MetaTrader installation.
Example command:
& 'C:\Program Files\MetaTrader 5\MetaEditor64.exe' /compile:'C:\Users\<user>\AppData\Roaming\MetaQuotes\Terminal\<terminal-id>\MQL5\Experts\codex\FVG.mq5' /log:'C:\Users\<user>\AppData\Roaming\MetaQuotes\Terminal\<terminal-id>\MQL5\Logs\codex-fvg-compile.log'
Adjust the compiled file and log path to the target being worked on.
Always read the log after compiling.
For the current EA example, the log is:
C:\Users\<user>\AppData\Roaming\MetaQuotes\Terminal\<terminal-id>\MQL5\Logs\codex-fvg-compile.log
Do not assume compilation succeeded just because the command returned exit code 0.
Check the log and report:
.ex5 file was produced or updated.