terrylica/cc-skills

log-reader

Read MetaTrader 5 log files.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/terrylica/cc-skills --skill log-reader

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

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.

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.

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 (TestPatternDetector, TestArrowManager)
  • 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

bash
/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:

bash
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:

  1. MT5 Log Files (this skill) - Human-readable Print() output
  2. 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

IssueCauseSolution
Log file not foundWrong date or pathVerify YYYYMMDD.log format and MQL5_ROOT env var
Empty log fileMT5 not running or no outputEnsure MT5 is running and Print() is being called
Encoding errorsUTF-16LE not handledRead tool handles encoding automatically
Missing test resultsTest not executedCompile and run test script in MT5 first
Grep finds nothingWrong patternUse case-insensitive (-i) or broader pattern
Old log dataLog rotationEach day creates new YYYYMMDD.log file
Path contains spacesUnquoted path variableQuote paths: "$LOG_FILE"
Sensitive data exposedTrading info in logsFilter sensitive fields when reporting to user

Post-Execution Reflection

After this skill completes, check before closing:

  1. Did the command succeed? — If not, fix the instruction or error table that caused the failure.
  2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
  3. Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
terrylica
Społeczność

academic-pdf-to-gfm

Convert academic PDF papers to GitHub-renderable GFM markdown with math equations. TRIGGERS - PDF, GitHub markdown, math

Instalacje / 1h
1
GitHub Stars
2
Aktualizacja
5 lis
terrylica
Społeczność

adr-code-traceability

Add ADR references to code for traceability. TRIGGERS - ADR traceability, code reference, document decision in code.

Instalacje / 1h
1
GitHub Stars
2
Aktualizacja
5 lis
terrylica
Społeczność

arxiv-source-first-paper-ingest

Read an arXiv paper faithfully by fetching the authors' own LaTeX source instead of OCR-ing the PDF. Extracts every display equation with its label, environment and enclosing proposition, renders each to MathML, and proves usability by compiling each formula with a real TeX engine. Use when you need a paper's formulas exactly — to replicate a method, implement a loss function or custom objective, verify a quoted number, or check a claim against what the authors actually wrote. TRIGGERS - read th

Instalacje / 1h
1
GitHub Stars
2
Aktualizacja
5 lis
terrylica
Społeczność

azure-provision

Bootstrap Azure automation when interactive az login is blocked by a Conditional Access policy (error 530035, "Device state: Unregistered"). Mints a service principal through the Azure Portal session ONCE — using Microsoft Graph over a captured token, not DOM clicking — then provisions resource groups, Cognitive Services / AI Language / Speech resources and their keys entirely via az/REST, writing key AND endpoint together into the SCS vault. Use when az login fails but the portal works, when mo

Instalacje / 1h
1
GitHub Stars
2
Aktualizacja
5 lis