agentleFS
Sign inStart free
kecoma1kecoma1/MQL5-SKILLS/skills/expert-advisors/SKILL.md

expert-advisors

Skill17 starsChanged 7 months agoMITView on GitHub

Use when creating or editing MQL5 expert advisors in this workspace. Follow the local conventions for EA structure, includes, classes, chart objects, and parameter declarations.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 working on .mq5 expert advisors or related .mqh files for this repository.

    line 8
  2. Distinctive:

    Always declare EA inputs using this pattern:

    line 12
  3. Very specific:

    Add an inline comment to every input.

    line 15
  4. Distinctive:

    Keep comments short and practical.

    line 16
  5. Distinctive:

    Use clear section names made of separators plus a title, for example:

    line 17
  6. Very specific:

    Do not leave input declarations without group or comment unless the user explicitly asks for a different style.

    line 28

≈ “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

Expert Advisors

Use this skill when working on .mq5 expert advisors or related .mqh files for this repository.

Inputs

Always declare EA inputs using this pattern:

  1. Group related parameters with input group.
  2. Add an inline comment to every input.
  3. Keep comments short and practical.
  4. Use clear section names made of separators plus a title, for example:
input group ".......... Data"
input int InpCandlesToLoad = 1000;       // Number of candles to load

input group ".......... Drawing"
input int InpPaintDurationMinutes = 120; // Line duration in minutes
input color InpFVGColor = clrDodgerBlue; // FVG color

Do not leave input declarations without group or comment unless the user explicitly asks for a different style.

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