Extract MQL5 articles and documentation. TRIGGERS - MQL5 articles, MetaTrader docs, mql5.com resources.
Extract technical trading articles from mql5.com for training data collection. Scope limited to mql5.com domain only.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
Use this skill when:
VALID requests:
OUT OF SCOPE:
If user requests non-mql5.com extraction, respond: "This skill extracts articles from mql5.com ONLY. For other sites, use different tools."
Working directory: $HOME/eon/mql5-local (adjust path for your environment)
Always execute commands from this directory:
cd "$HOME/eon/mql5-local"
Format: https://www.mql5.com/en/articles/[ID]
Example: https://www.mql5.com/en/articles/19625
Action: Extract single article
Format: Numeric (e.g., 29210372) or username (e.g., jslopes)
Source: From mql5.com profile URL
Action: Auto-discover and extract all user's articles
Format: Text file with one URL per line Action: Batch process multiple articles
If user says "extract mql5 articles" without specifics, prompt for:
For detailed information, see:
| Issue | Cause | Solution |
|---|---|---|
| Non-mql5.com URL | Skill only supports mql5.com | Use other tools for non-mql5.com sites |
| Article not found | Invalid article ID or removed | Verify URL exists by visiting in browser |
| User ID not recognized | Wrong user ID format | Use numeric ID from profile URL or exact username |
| Empty extraction | Rate limiting or site change | Wait and retry, check for site structure changes |
| Permission denied | Working directory mismatch | Run from $HOME/eon/mql5-local directory |
| Batch too large | Too many articles requested | Limit batch size, use URL list file |
| Missing dependencies | Required tools not installed | Install curl, jq for extraction |
| Output encoding issues | Unicode in article content | Ensure UTF-8 output handling |
After this skill completes, check before closing:
Only update if the issue is real and reproducible — not speculative.