Analyze an editor, build, or structured trace log (Unreal Engine Saved/Logs, Unity Editor.log, Godot output, MSVC/UBT/MSBuild build output, JSONL / structured .jsonl traces, or any text log) token-efficiently. Use when the user mentions checking, reading, searching, summarizing, or diffing a log; investigating editor/engine errors, warnings, crashes, asserts, callstacks, or log spam; or asks "what's flooding the log" / "what changed since the last run". Parses, deduplicates, classifies by severity/category, and extracts decisive fields via the gamedev-log CLI instead of dumping the raw file (logs can be tens of MB).
$npx -y skills add jsungmin/vs-token-safer --skill logsInstalls into the current project.
Run `npx skills use "https://github.com/jsungmin/vs-token-safer" --skill "jsungmin/vs-token-safer/logs"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/jsungmin/vs-token-safer" that are relevant to the current task. Run `npx skills add "https://github.com/jsungmin/vs-token-safer"` and select the relevant skills, then follow their instructions.