skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
tmaru-eng/strategy-bricks126 installs

mql5-docs-research

Research MQL5 documentation (Japanese and English only) for MQL5 creation/editing issues, compile errors, or API questions. Use when users ask to look up docs, interpret MQL5 errors, or confirm correct language usage. Sources limited to https://www.mql5.com/ja/docs and https://www.mql5.com/en/docs.

How do I install this agent skill?

npx skills add https://github.com/tmaru-eng/strategy-bricks --skill mql5-docs-research
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill researches MQL5 documentation from official sources. It is generally safe but has a minor exposure to indirect prompt injection because it processes external web content without explicit boundary markers.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    1 file scanned · No issues

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

MQL5 Docs Research (JA/EN)

Provide doc-based guidance when users hit errors while creating or modifying MQL5 code. Use only the official docs in Japanese and English.

Scope and Sources

Inputs to Collect

Ask for any missing context before research:

  • Exact error text and error code (if any)
  • File path and line/column numbers
  • MQL5 file type (.mq5 or .mqh)
  • Related API/class names (e.g., CTrade, MqlRates)
  • MetaTrader 5 build/version (if available)

Workflow

  1. Normalize the error or question into keywords:
    • Extract error code and symbols (function/class names)
    • Keep 2-5 keywords for searching
  2. Search Japanese and English docs:
    • Use site search in the docs pages
    • If no direct hit, search broader sections by keyword
  3. Open the most relevant doc pages and confirm:
    • Correct function signatures
    • Parameter types and constraints
    • Return values, error handling, and examples
  4. Produce a response in Japanese with:
    • Summary of the cause
    • Doc links (JA first, EN second)
    • Specific guidance aligned with doc wording
    • Next checks (if ambiguity remains)

Output Format (Markdown)

  • Summary (1-3 sentences)
  • Relevant Docs
    • JA: <url>
    • EN: <url>
  • Key Notes (bullets)
  • Next Checks (bullets, optional)

Guardrails

  • If the error cannot be mapped to docs, state that clearly and propose a best-effort hypothesis.
  • Never invent API signatures or behavior not documented in the official docs.
  • Keep the response concise and actionable.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/tmaru-eng/strategy-bricks/mql5-docs-research">View mql5-docs-research on skillZs</a>