⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

MT5日志读取器 - 自动读取MetaTrader 5日志文件，无需手动检查智能交易面板

log-reader by terrylica/cc-skills

69 周安装量

33 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/terrylica/cc-skills --skill log-reader

自动化调试金融科技

🇨🇳中文介绍

MT5 日志读取器

直接读取 MetaTrader 5 日志文件，以访问来自指标、脚本和智能交易系统的 Print() 输出，无需手动检查“智能交易”面板。

目的

实现“选项 3”双重日志记录模式：

Print() - MT5 日志文件（可通过“智能交易”面板人工读取）
CSV 文件 - 结构化数据（用于程序化分析）

Claude Code 可以在无需用户干预的情况下自主读取这两种输出。

何时使用此技能

在以下情况下使用此技能：

验证 MT5 指标/脚本执行情况
检查编译或运行时错误
分析 Print() 调试输出
验证单元测试结果（Test_PatternDetector, Test_ArrowManager）
用户提到手动检查“智能交易”面板

日志文件位置

MT5 日志存储在：

$MQL5_ROOT/Program Files/MetaTrader 5/MQL5/Logs/YYYYMMDD.log

文件格式：

编码：UTF-16LE（小端序）
结构：制表符分隔的字段（时间戳、来源、消息）
大小：全天增长（通常为 10-100KB）

使用说明

1. 构建今日日志路径

/usr/bin/env bash << 'SKILL_SCRIPT_EOF'
# 确定当前日期
TODAY=$(date +"%Y%m%d")

# 构建绝对路径
LOG_FILE="$MQL5_ROOT/Program Files/MetaTrader 5/MQL5/Logs/${TODAY}.log"
SKILL_SCRIPT_EOF

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

2. 读取整个日志文件

使用 Read 工具：

文件路径：步骤 1 中的绝对路径
该文件包含来自 MT5 指标/脚本的所有 Print() 语句
UTF-16LE 编码由 Read 工具自动处理

3. 搜索特定内容（可选）

使用 Grep 过滤条目：

Pattern: indicator name, "error", "test.*passed", etc.
Path: Log file path from step 1
Output mode: "content" with -n (line numbers)
Context: -A 5 for 5 lines after matches

4. 分析最近条目（可选）

使用 Bash 的 tail 命令查看最新输出：

tail -n 50 "$LOG_FILE"

检查单元测试结果

搜索测试通过/失败指示器：

Pattern: test.*passed|test.*failed|Tests Passed|Tests Failed|ALL TESTS PASSED
Output mode: content
Context: -B 2 -A 2

Pattern: error|ERROR|warning|WARNING|failed to create
Output mode: content
Context: -A 3

Pattern: CCI Rising Test|PatternDetector|ArrowManager
Output mode: content
Context: -A 2

查看初始化消息

Pattern: OnInit|initialization|Initialization complete|Phase \d+
Output mode: content

示例 1：验证单元测试完成情况

Input: User compiled Test_PatternDetector.mq5
Action:
  1. Read today's log file
  2. Grep for "Test.*PatternDetector|Tests Passed|Tests Failed"
  3. Report results (e.g., "17 tests passed, 0 failed")
Output: Test status without user checking Experts pane

示例 2：检查运行时错误

Input: User reports indicator not working
Action:
  1. Read today's log file
  2. Grep for "ERROR|error|failed" with -A 3 context
  3. Analyze error messages
Output: Specific error details and line numbers

示例 3：验证阶段 2 箭头创建

Input: User asks "did the test arrow get created?"
Action:
  1. Read today's log file
  2. Grep for "Phase 2|Test arrow created|Failed to create"
  3. Check for success/failure messages
Output: Arrow creation status with timestamp

日志文件可能包含敏感的交易数据（品种名称、账户信息）
仅限于 Read、Bash、Grep 工具（不允许通过 WebFetch 进行网络访问）
不要在不必要的情况下在面向用户的输出中暴露绝对路径
报告结果时过滤敏感信息
不允许文件修改操作

与双重日志记录的集成

此技能实现了对双重日志记录模式其中一半的程序化访问：

MT5 日志文件（此技能）- 人类可读的 Print() 输出
CSV 文件（CSVLogger.mqh）- 用于验证的结构化审计跟踪

两者都可在无需用户干预的情况下访问：

MT5 日志：通过此技能读取
CSV 文件：通过 Read 工具或 validate_export.py 直接读取

使用此技能时：

存在今日日期的日志文件
文件大小 > 0（非空）
包含预期的指标/脚本输出
时间戳与执行时间匹配
错误消息（如果有）是可操作的
测试结果（如果适用）显示通过/失败计数

MT5 文件位置：docs/guides/MT5_FILE_LOCATIONS.md
双重日志记录实现：docs/plans/cci-rising-pattern-marker.yaml 阶段 3-4
CSVLogger 库：Program Files/MetaTrader 5/MQL5/Indicators/Custom/Development/CCINeutrality/lib/CSVLogger.mqh

问题	原因	解决方案
日志文件未找到	日期或路径错误	验证 YYYYMMDD.log 格式和 MQL5_ROOT 环境变量
日志文件为空	MT5 未运行或无输出	确保 MT5 正在运行且 Print() 被调用
编码错误	未处理 UTF-16LE	Read 工具自动处理编码
缺少测试结果	测试未执行	首先在 MT5 中编译并运行测试脚本
Grep 未找到任何内容	模式错误	使用不区分大小写（-i）或更宽泛的模式
旧日志数据	日志轮换	每天创建新的 YYYYMMDD.log 文件
路径包含空格	路径变量未加引号	为路径加引号："$LOG_FILE"
敏感数据暴露	日志中包含交易信息	向用户报告时过滤敏感字段

🇺🇸English

MT5 Log Reader

Read MetaTrader 5 log files directly to access Print() output from indicators, scripts, and expert advisors without requiring manual Experts pane inspection.

Purpose

Implement "Option 3" dual logging pattern:

Print() - MT5 log files (human-readable via Experts pane)
CSV files - Structured data (programmatic analysis)

Claude Code can autonomously read both outputs without user intervention.

When to Use This Skill

Use this skill when:

Validating MT5 indicator/script execution
Checking compilation or runtime errors
Analyzing Print() debug output
Verifying unit test results (Test_PatternDetector, Test_ArrowManager)
User mentions checking "Experts pane" manually

Log File Location

MT5 logs are stored at:

$MQL5_ROOT/Program Files/MetaTrader 5/MQL5/Logs/YYYYMMDD.log

File Format :

Encoding: UTF-16LE (Little Endian)
Structure: Tab-separated fields (timestamp, source, message)
Size: Grows throughout day (typically 10-100KB)

Instructions

1. Construct today's log path

/usr/bin/env bash << 'SKILL_SCRIPT_EOF'
# Determine current date
TODAY=$(date +"%Y%m%d")

# Build absolute path
LOG_FILE="$MQL5_ROOT/Program Files/MetaTrader 5/MQL5/Logs/${TODAY}.log"
SKILL_SCRIPT_EOF

2. Read the entire log file

Use Read tool:

File path: Absolute path from step 1
The file contains all Print() statements from MT5 indicators/scripts
UTF-16LE encoding is automatically handled by Read tool

3. Search for specific content (optional)

Use Grep to filter entries:

Pattern: indicator name, "error", "test.*passed", etc.
Path: Log file path from step 1
Output mode: "content" with -n (line numbers)
Context: -A 5 for 5 lines after matches

4. Analyze recent entries (optional)

Use Bash with tail for latest output:

tail -n 50 "$LOG_FILE"

Common Validation Patterns

Check unit test results

Search for test pass/fail indicators:

Pattern: test.*passed|test.*failed|Tests Passed|Tests Failed|ALL TESTS PASSED
Output mode: content
Context: -B 2 -A 2

Find compilation errors

Pattern: error|ERROR|warning|WARNING|failed to create
Output mode: content
Context: -A 3

Monitor specific indicator

Pattern: CCI Rising Test|PatternDetector|ArrowManager
Output mode: content
Context: -A 2

View initialization messages

Pattern: OnInit|initialization|Initialization complete|Phase \d+
Output mode: content

Examples

Example 1: Validate unit test completion

Input: User compiled Test_PatternDetector.mq5
Action:
  1. Read today's log file
  2. Grep for "Test.*PatternDetector|Tests Passed|Tests Failed"
  3. Report results (e.g., "17 tests passed, 0 failed")
Output: Test status without user checking Experts pane

Example 2: Check for runtime errors

Input: User reports indicator not working
Action:
  1. Read today's log file
  2. Grep for "ERROR|error|failed" with -A 3 context
  3. Analyze error messages
Output: Specific error details and line numbers

Example 3: Verify Phase 2 arrow creation

Input: User asks "did the test arrow get created?"
Action:
  1. Read today's log file
  2. Grep for "Phase 2|Test arrow created|Failed to create"
  3. Check for success/failure messages
Output: Arrow creation status with timestamp

Security Considerations

Log files may contain sensitive trading data (symbol names, account info)
Restricted to Read, Bash, Grep tools only (no network access via WebFetch)
Do not expose absolute paths unnecessarily in user-facing output
Filter sensitive information when reporting results
No file modification operations allowed

Integration with Dual Logging

This skill enables programmatic access to one half of the dual logging pattern:

MT5 Log Files (this skill) - Human-readable Print() output
CSV Files (CSVLogger.mqh) - Structured audit trails for validation

Both are accessible without user intervention:

MT5 logs: Read via this skill
CSV files: Read directly via Read tool or validate_export.py

Validation Checklist

When using this skill:

Log file exists for today's date
File size > 0 (not empty)
Contains expected indicator/script output
Timestamps match execution time
Error messages (if any) are actionable
Test results (if applicable) show pass/fail counts

References

MT5 file locations: docs/guides/MT5_FILE_LOCATIONS.md
Dual logging implementation: docs/plans/cci-rising-pattern-marker.yaml Phase 3-4
CSVLogger library: Program Files/MetaTrader 5/MQL5/Indicators/Custom/Development/CCINeutrality/lib/CSVLogger.mqh

Troubleshooting

Issue	Cause	Solution
Log file not found	Wrong date or path	Verify YYYYMMDD.log format and MQL5_ROOT env var
Empty log file	MT5 not running or no output	Ensure MT5 is running and Print() is being called
Encoding errors	UTF-16LE not handled	Read tool handles encoding automatically
Missing test results	Test not executed	Compile and run test script in MT5 first
Grep finds nothing	Wrong pattern	Use case-insensitive (-i) or broader pattern
Old log data	Log rotation	Each day creates new YYYYMMDD.log file
Path contains spaces	Unquoted path variable	Quote paths: "$LOG_FILE"
Sensitive data exposed	Trading info in logs	Filter sensitive fields when reporting to user

Weekly Installs

Repository

terrylica/cc-skills

GitHub Stars

First Seen

Jan 24, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode59

gemini-cli58

codex57

claude-code56

cursor56

github-copilot56

Skills CLI 使用指南：AI Agent 技能包管理器安装与管理教程

52,700 周安装