agentleFS
Sign inStart free
kecoma1kecoma1/MQL5-SKILLS/skills/compile-mql5/SKILL.md

compile-mql5

Skill17 starsChanged 7 months agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when compiling .mq5 files in this repository.

    line 8
  2. Very specific:

    Use MetaEditor64.exe from the local MetaTrader installation.

    line 12
  3. Distinctive:

    Always read the log after compiling.

    line 24
  4. Very specific:

    Do not assume compilation succeeded just because the command returned exit code 0.

    line 30
  5. Distinctive:

    Check the log and report:

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compile MQL5

Use this skill when compiling .mq5 files in this repository.

Command

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.

Log Review

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:

  1. Number of errors.
  2. Number of warnings.
  3. Important file paths mentioned by the compiler.
  4. Whether the expected .ex5 file was produced or updated.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free