What problem does it solve? Debugging C4 framework applications from raw NLog trace logs is slow and error-prone: log files are large, multiline stack traces break naive parsing, and inconsistent plugin naming makes filtering unreliable. This Skill imports .log files into a queryable SQLite database and guides correct interpretation of fields, error patterns, and stack traces. ## Core Features & Use Cases - Automatic database bootstrap: Detects or creates trace_logs.db by running the nlog_import.py importer, then opens it through the sqlite-logs MCP server for SQL querying. - C4-aware log interpretation: Documents the pipe-delimited record format, plugin naming inconsistencies (always filter with LIKE '%plugin%'), process/thread correlation, and common error patterns such as ValidationException and unhandled framework exceptions. - Source code cross-referencing: When the VS MCP server is available, enriches findings with Roslyn-based symbol lookups, caller/callee analysis, and method body inspection. - Use Case: Ask "what errors happened in the MBSecure plugin yesterday" and get the first root-cause exception, its call chain, affected process IDs, and the relevant C# method source. ## Quick Start Ask the assistant to analyze the logs in the current folder, for example by saying "analyze the logs and show me all ERROR entries grouped by plugin".